We have different groups of people who work with FogBugz, including outside clients. We'd like to have different labels for different clients, so that one client sees 1 - Showstopper and another sees 1 - Urgent.
|
1
|
|
|
|
|
2
|
Unfortunately, Priorities are Site Wide and can not be restricted/changed based on groups or projects. To can always use tags to manually work around grouping your tickets within a project. |
||
|
|
|
1
|
You can configure users within a group and configure a single client in a project. I'm not aware of a way to link a group to a priority. You could create a number of projects named: ShowStoppers, Urgent, etc. However, I would see that as a bit confusing and it would remove the usefulness of the real Priority field. Why not just create a one or more project(s) per group, where each group represents a client? I suppose you could have one user per group, if you wanted to get that granular. |
||
|
|
|
0
|
While FogBugz does let you customize the labels associated with each priority, these labels are global across all projects. This is a very interesting use case for priorities, and I think it may be useful to other FogBugz users, but it is not a feature that is currently on our development schedules. My initial thought is that, although the implementation of group-specific priority labels may not be very difficult in and of itself, I can envision it opening up a whole new set of requests that could add unwanted complexity to FogBugz. For example, I can foresee requests to have one set of priorities for external users that map to a different set of priorities for internal users. |
||
|
|
