Can Jira Cloud restrict Resolution Types based on Issue Type?

[Dwight Holman]

We currently do this in JIRA server using a 3rd party app. Unfortunately the app is not available for Cloud yet, and is one of our blockers in migration to the cloud.

For example; our support project (for a hardware & software product) has issue types "Bug", "Documentation" and "Hardware".

• A "Fixed" resolution is applicable for an issue of type "Bug", but not a request about a hardware failure.
• The "Hardware replaced" resolution is valid for an issue of type "Hardware", but makes no sense for a "Bug".
• The "Not a bug" resolution is good for "Bug" types, but doesn't apply to issues of type "Documentation".

Maybe we have more issue types than other teams. But this helps us to see patterns in support activity.

From Community Discussion I see JIRA can restrict Resolution by using different workflow states for different issue types, and then excluding/including resolutions in the workflow properties. But given the number of issue types and resolutions it seems this approach would be very clumsy, time-consuming to validate, and hard to maintain.

I've searched and have not yet found a good solution for this.

If it makes any difference we currently expect to use classic projects in Jira Cloud because Next-Gen ones are lacking some things we want (though I know this keeps changing).

Does anyone else do this kind of thing in JIRA Cloud?

Maybe we should have more 'generic' issue types, and differentiate issues based on Components (or other fields), but it seems our agents would continue to assign resolutions that don't make sense.

Suggestions and ideas welcome.

[Fabian Lim · Accepted solution]

Hi @Dwight Holman

I'm assuming you are referring to extended schemes (https://marketplace.atlassian.com/apps/1214172/extended-schemes-for-jira?tab=overview&hosting=server).

Without it it will be hard to manage it.  I suggest you use scripting with powerscripts which introduces the concept of live fields and you can hide/show resolutions based in issue types. Link: https://confluence.cprime.io/plugins/servlet/mobile?contentId=6558155#content/view/6558155

They have excellent support so if you get stuck, please contact them.

[Dwight Holman]

Thanks for the suggestion @Fabian Lim - indeed that app looks like it would do what we want. Have you used it to manipulate the Resolution field before?

Of course we could migrate without solving this - and then add it later. But good to have options.

[Fabian Lim]

Yes, this is what you would use:

https://confluence.cprime.io/plugins/servlet/mobile?contentId=6558199#content/view/6558199