0

My understanding is case numbers just keep incrementing across my entire account. (e.g. Case 1 was the default case in the inbox, 2,3,4 were cases in my first project)

Is it possible to customize the case numbers on a per project basis.

I'd like (especially if I have multiple customers logging cases on multiple projects) to have each project have it's own case counter and be prefixed by some identifying code. (similar to how JIRA works).

e.g.

Project: FooApp

  • Foo-1
  • Foo-2
  • Foo-3

Project: BarApp

  • Bar-1
  • Bar-2
  • Bar-3
flag

1 Answer

2

This is not supported by the FogBugz database design - case numbers are "global" across all projects for a FogBugz installation.

In practice, I've not found this to be necessary - judicious use of filters and search patterns has provided all the orthoganility I have required.

link|flag
Thanks for the clarification James. Maybe you could provide a bit more info. I have 2 projects on the go right now. One for Client A / One for Client B. Each client has a FB Account (restricted to their project) for the purpose of logging bugs/issues/support requests. However I'd prefer that each Client didn't have any indication what volume of work/case the other client was generating. If that makes sense :-). Thanks again. – Eoin C Oct 11 at 21:45
Hi Eoin, I had wondered if that was your situation. The only work-around I can think of is to ask Fog Creek whether your licence allows you to deploy two separate instances of FogBugz, one for each customer. This is a bit of a hack, I admit; perhaps someone else will be able to come up with a better idea. On the other hand, is it bad for your customers to know you are in demand? You could also set up a third "internal" customer (for internal infrastructure issues, etc), and claim that the other cases are a mix of internal and the other client's... – James McLeod♦ Oct 11 at 23:54

Your Answer

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