I understand that there is no technical connection between a status and a resolution. But from a developer/user perspective, there usually is.
For example, in our team the only valid combination of status and resolution for status "Resolved" is resolution "fixed". All of the other resolutions will be used in our system to indicate a reject with a particular reason or a duplicate.
Is there a way to enforce this?
In a way. Create 2 transitions; 'Resolved and Closed' and 'Other Closed'. In the post function for Resolved and closed set the resolution with a post function and don't put it on the transition screen. for Other Closed put the resolution field on the transition screen and only allow the resolutions other than 'fixed' with the workflow properties.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs