We are setting up a specific list of Resolution fields (listed below) to be used and should be treated as Unresolved / Resolved:
Resolution field name Should be treated as
Won't Fix Unresolved
Works As Designed Resolved
Works For Me Resolved
I have got these fields added to Resolutions. However, as per the article below, if I have any thing updated to Resolution field, JIRA will consider that to be resolved and will add a green check under "Issues in this Epic" section of Epic view and a strike through on the issue on Agile (SCRUM) Board.
Isn't there a way to have above listed resolutions treated as mentioned by JIRA so that these can be used appropriately.
This won't work.
If the resolution field is set, then the issue is resolved. If it is empty, it is unresolved.
You'd need to rewrite JIRA and a lot of its add-ons to change that. It would be a big project to undertake on Server, and you'd never get any of it into Cloud.
On Server, you could bodge it - have your own "resolution" field, and then populate the actual resolution with a listener in the background so that it's empty for your unresolved items and filled for the resolved ones, but that's still not going to look right.
Your best option is to use the resolution field properly, not break your data with this poor design.
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