17

2

I've seen the feature request to allow for custom fields on a per-project basis (custom fields plugin). I'd like to see custom categories per project as well (workflow plugin).

Fog Creek Case FC1864314

flag

3 Answers

3

We have a case open to consider this feature for a future release. Please up-vote this question to show your support for adding this feature.

link|flag
1

The problem with custom categories per project is that it gets complicated when moving cases between projects.

You may have categoryx in one project but not any other.

Currently, FogBugz can't handle moving a case of categoryx out of the project and into a project that doesn't have categoryx - it doesn't know what category to make it.

One solution may be to have a default category marked for any incoming case with an unsupported category. However, it's probably more complicated than that.

I do agree it would be nice to have if it doesn't make FB more complicated.

link|flag
Great feedback, Marc. Thanks! – Rob Sobers Mar 15 2010 at 11:28
the current behavior is that you have a default category for new cases (globally). if this feature was implemented, you would simply set your default category per-workflow or per-project (more likely the former). It wouldn't be much different than moving a case to a project with different statuses defined. when you change the project field, the category field would switch to a valid category for that project – adambox Mar 17 2010 at 20:15

Your Answer

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