Hi, I want to customize the possible resolutions that an issue will have, depending on the project that the issue belongs to.
Since Resolution is not a custom field, Do you know how can I do that? is this possible to do in a clean & neat way? Thanks!
Community moderators have prevented the ability to post new answers.
You can, but it's not a lot of fun. There are no "resolution schemes", you have to set a list of resolutions that will be used globally.
But, you can then use "workflow properties" to shorten the available options from the global list when an issue is in a particular status. So, if you're happy to have different workflows per project (and/or issue type), then yes, you can limit the resolutions.
Hi Pablo,
this is one of the oldest and most voted issues for Jira: https://jira.atlassian.com/browse/JRA-3821
You can have different resolutions for different workflows with workflow properties as Jobin described here:
https://answers.atlassian.com/questions/192090
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you specify what exactly Jobin describes? There are so many additional comments that referring to a link doesn't make sense as time passes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You could also use a plugin for this. https://marketplace.atlassian.com/plugins/com.develocenter.jira.links-scheme/server/overview
Been using it at a enterprise size customer with good results.
Good luck!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I like the 'include' workflow property. It allows me to restrict the options at every resolution point in the workflow by issue type. For instance, we have a close option from open, but only certain resolutions like Duplicate, Working as Designed, Withdrawn by User make sense that early in the workflow so they are the only ones listed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you provide an example?
I am also looking to restrict the resolution options per project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Limiting resolution options
Use the jira.field.resolution.include workflow property
for exampl jira.field.resolution.include =1,2,3 where 1,2,3 are the resolution ids
https://confluence.atlassian.com/adminjiraserver071/workflow-properties-802592825.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is an open request in the Atlassian JIRA (Open and created in 2004 ...) :
https://jira.atlassian.com/browse/JRA-3821
You can define different resolutions not per project but per workflow.
Add in the workflow properties jira.field.resolution.exclude or jira.field.resolution.include
:
https://confluence.atlassian.com/adminjiraserver073/workflow-properties-861253674.html
There are also some add-on available :
https://marketplace.atlassian.com/search?query=resolution
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Community moderators have prevented the ability to post new answers.
Welcome to great meetings, with less work. Automatically record, summarize, and share instant recaps of your meetings with Loom AI.
Learn moreOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.