2

Hello,

I have been using Jira extensively and am thinking of moving to FogBugz. We want to use this for multiple projects. One of the nice things Jira does is allow for prefixes to be linked with issues. So for example, the first issue say for Project A may be

A-1, the second A-2, etc.

If i have another project, say Project B, it could then have

B-1, B-2, etc.

It looks like case numbers are purely numeric and incremental. I realize that there is a project field which I am guessing how this is supposed to be conveyed. But saying

Can you look at case 1043 versus can you look at A-1043 has two different results. In the former, if you have multiple projects, you have potentially look up with 1043 is to determine the project context. The latter allows you to instantly know it is 1043.

Of course, you should be able to move issues over from one project to another.

Thanks!

flag
1 
Not to point out the obvious, but if you're just worried about "saying" which case to go look at and providing a project context, you can still say go look at A-1043 and then just simply search for case 1043. It doesn't have to be any more complicated than that. I'm pretty sure FB doesn't have a way to change the case ID from anything but sequential numbers. It'll just have to be something you get use to. – bitbounce Jan 6 2011 at 14:26
If you are dealing with multiple projects concurrently, it makes it a bit easier to manage and discuss issues. Obviously you can do as you state. Bear in mind, if you don't know offhand that 1043 is from A, you have to first look to do what you want wrote which is ... "you can still say go look at A-1043". This is a personal preference based on experience on working on many projects at once. Small cues to context without having to look up things, for some, is convenient and helpful. – Ben Jan 7 2011 at 5:13

1 Answer

1

FogBugz allows you to change the prefix used for case numbers, but this is a global setting (i.e., it applies to all case numbers regardless of the project they belong to). As you mention in your question, the Project field is meant to convey the project context rather than a project-specific case number prefix.

Out of curiosity, how does Jira's system handle the following situation: Create case A-X in project A, move it to project B, then back to project A at some later date. Does the case keep the same A-X number when it's returned to project A? Or does that number get incremented every time the project is changed?

link|flag
Do you know if there are any plans to add such functionality. Many of the people I work with have found this to be an incredibly useful feature. I believe the behavior in Jira for managing the numbers upon return is not great. So if you switch A-X to B, you'd get say B-Y. If you returned to A, you'd get A-Z. I think I did it once and was a bit annoyed that it did this. There is a Jira issue opened for this: jira.atlassian.com/browse/JRA-13659 – Ben Jan 7 2011 at 5:24
We do not currently have any plans to change this functionality, but if enough interest is shown by our customers we'll certainly re-examine the idea. Dealing with the cross-project numbering problem feels tricky to me. Even if we were to handle the "move a case from project A to project B & then back to project A" in a better way, you can still end up having multiple case numbers that all map to the same underlying case, which sounds like it could be confusing. Also, what happens to the B-Y number when you move the case back to project A? Does it redirect to A-Z? What about the original A-X? – db Jan 7 2011 at 16:33

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.