I have created a new issue type in my JIRA. Say, for example, it's called Incident. Now I am creating custom workflow which will be then used for issues of that type.
Under the Issue Attributes → Resolutions section there are some predeclared out of the box resolutions such as "Fixed", "Won't fix", "Duplicate" and so on, and it gives me an ability to create my own new resolutions.
Now the most important point. How can I create and configure a number of resolutions so that these new resolutions will only be available for issues of my specific type (Incident), and unavailable for issues of any other types? At the same time, out-of-the-box resolutions must be unavailable for Incident-issues.
Resolutions are global, they don't have contexts or schemes like custom fields do. It's a single list, available to all issues irrespective of issue type or any other data.
However, you can do it with a bit of work.
It is NOT directly related to issue type though, it's done via workflow. In JIRA, you can associate different workflows with different issue types and projects. So you can set up something like:
So, five project/issuetype combinations, but only three workflows. The trick to restricting resolutions is done at a workflow level, so if you do this for the "task workflow", it's important to understand that you will affect AAA-Task, BBB-Task and AAA-Feature.
The trick itself is documented at https://confluence.atlassian.com/display/JIRA/Workflow+properties
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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