by Mikey Schott, ServiceRocket Trainer
Does your HR team use JIRA? Have they ever closed out your expense report with a resolution of 'Fixed'? Or, perhaps, more awkwardly, have they ever closed out your request for maternity leave with a resolution of 'Cannot Reproduce'? If a wide variety of teams at your organization use JIRA, chances are that some resolution field values just plum don't make any sense for some projects. The general rule of thumb for resolutions in JIRA is to make them as generic as possible so that they can apply to a variety of projects. However, if that's not good enough for you, we'll let you in on another dark, little JIRA Administration secret – the not-entirely-supported resolution include and resolution exclude transition properties (see JIRA Workflow properties).
Both of these transition properties, in their own way, allow you to choose a subset of your resolutions to be available during a transition. In this tutorial video, I demonstrate why you might want to use these properties, how to configure them, and end with a warning on why you might not want to use them. I also sort-of pretend to be Batman.
Call for Comments
- By customizing resolution statuses to meet the needs of different groups, how could it impact user adoption of JIRA across your organization?
