As a schema admin I want to be able to specify the order of reasons for issue/field sets on a per issue basis.
As an end user I want the order of reasons for issue/field sets to be respected in the distribution section when viewing or creating an issue. E.g. If the order is "For Checking", "For Review", and "For Approval" then I want that to be the order when viewing or setting the issue distribution.
Specify the order of reasons for issue/field sets at the schema level.
Inherit or override at the following levels:
Sub-schema.
Folder Type.
Issue Type.
When viewing an issue, show the reasons for issue/field sets in the specified order.
When creating/sending an issue, show the reasons for issue/field sets in the specified order.
Practical use of functionality?
As above |
|
What is the impact of not doing this?
Confusion for users in workflows with complex distributions. Users would however get a better and less frustrating user experience on all Issues |