I've found a little problem by accident:

  1. I have two projects, numbered 100 and 200
  2. I've added several cases to each project. They were assigned squential numbers (100-1,100-2,100-3,100-4, 200-1,200-2)
  3. Later I've noticed case 100-4 related to bad project by my own mistake. So I edit the case (100-4) and save it as project #200 case (which is possible per GUI)
  4. The "moved" case was given 200-4 (yes, the new project number combined with the old case number)
  5. Then I add two more new cases to project #200. Now I have cases numbered 200-1,200-2,200-3, 200-4,200-4

In fact, the duplicate 200-4 does not harm Drupal - because every case is separate node - but for human users it is confusing, isn't it?

Comments

jjrosent’s picture

jjrosent commented

We ran into this too and I think needs to be thought about. Our solution was to remove individual case numbering across all projects. Instead our cases all increment from the same pool. In this way a new case made under project 100 is 100-1 and now a new case made under project 200 is 200-2. We didnt particularly like the project-case encoding at all so this was a great solution for us, as long as we can continue it through future casetracker upgrades :)

jmiccolis’s picture

jmiccolis commented
Version: 5.x-1.3-beta1 » 6.x-1.x-dev
Status: Active » Fixed

Because of issues like this and the simple fact that these numbers caused each project and case node to have multiple numeric identifiers they have been removed from the D6 version.

As in mentioned above this shouldn't cause issues upgrading as internally these aren't used at all.

Changing version to 6.1 & setting to 'fixed' ;)

whiteb’s picture

whiteb commented

I am not sure I follow you. Are you saying that case tracker in D6 won't have case numbers?

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.