Question

We're using the workflow plugin and would like to add a couple of categories which fall outside of the scope of software development (such as IT orders for example, which would be used only by the IT group) and we're worried that it would clutter the interface and confuse users with too many options.

One possible approach could be if you could somehow configure permissions for categories by using groups. So that in our case only members of the "IT" group would be able to see (and work with) cases of category "IT order".

Alternatively this could be solved by being able to configure whether a field should be displayed or not per category.

Case FC1838029

Answer 1

Case filed for "Being able to configure whether a field should be displayed or not per category. This would in effect serve the same purpose of not cluttering the UI with fields that only apply for a specific category."

Definitely handy if a site were to have more than 5 relatively unique categories. I'm thinking that fields hidden upon category switch would keep their data in the event that the category was switched back.

Answer 2

We thought about this, and it would be kind of nice to be able to limit categories to certain groups, but categories and permissions are so much a part of the core of FogBugz that this ended up looking like a lot of coding and design work, far more than would be warranted by the potential benefit. Additionally, we wanted our workflow plug-in to be as lightweight as possible, as even the simplest workflow management can get confusing.

If we had unlimited resources, this would already be done. As it stands, many other features outweigh it from a cost-benefit standpoint.

Answer 3

For per-category Custom Fields, see this question

Answer 4

I would also love to see the ability to set filed visibility per category. Minimalism is one of the reasons I am considering to use FogBugz.

Some use-cases where this feature would be useful: 1. Bug category - typically needs several unique fields like version, operating system, etc. 2. Folder category - A 'Folder' case is sometime useful to keep a well structured case tree. 'Folder' case does not need most fields.