So, we have a beautifull workflow, with 6 steps, which you have to follow in order to close an issue.
(Open, Dev, Test, Acc, Prod, ok, Close)
BUT sometimes when you're in an "earlier" step, e.g. Open, Dev, Test or Acc, it's a Won't fix and you want to close the issue.
I don't want to edit my workflow because I don't want extra transition-buttons in my screen, but how can I close my issue then? Is that even possible?
I have found out that with an extra Tab on e.g. an Edit-screen, I can change the Resolution. Is there some way you can set validators or something like that to react on that?
Hope you can help me!
Status is not a field, it's an indication of where you are in the workflow.
To change status, you must use transitions.
p.s. Never put the resolution on an edit screen. Anyone making any edits to open issues will resolve them, and yet leave them open.
It's even worse (I've fooled around with adding it to a tab so it can be used on Edit-screen).... The default option for the Resolution screen is "Done". So, when you edit an issue and do nothing with that tab, the issue will by default become "Done".
p.s. adding a Resolution "Unresolved" is not the same as the JIRA-resolution called Unresolved (the italic written one)
The tab is part of the edit screen. It is just a visual organization, not another screen. The RED unresolved value indicates the field is NULL in the database. The only way to clear it is to go through a transition with a post function that clears the resolution field. the default workflow reopen transition does that if you need an example on how to set it up. Also, I suggest not having a default since most people will just leave it and you won't get the real one when you should.
If you have the proper permission, Create a Global Transition in your workflow from any status to the "Close" transition, add a transition screen for that and make sure that the "Resolution" field is in there so it can be populated on this transition.
As Nic pointed out, Remove the Resolution field in the edit screens.
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