I have successfully added Post Functions to each step of my workflow such that the resolution of the issue is cleared when it is transitioned from one step to the next.
My issue now is that I cannot figure out how to keep that resolution field clear when the ticket is updated throughout the course of backlog grooming or similar. I found some documentation that suggested I check the "Edit" operation in my Project Screen Scheme, but I've dead-ended here.
The behavior I am trying to prevent is that the resolution field is updated every time a ticket is edited but the workflow is not touched. This results in the ticket appearing to be struck through on our Backlog view.
You need to remove the resolution field from the edit screen, it should only be put on the view and transition-to-closed-type-status screens.
Go to the project admin and look for "issue type screen scheme", amend that and you'll see it has one or many "screen schemes" associated with one or many issue types. You need to go into each one of these and look for the "screens" that are used by the "create" and "edit" actions. Go into each one of these, and remove the resolution from the list
Thanks for the speedy reply. Will doing this still allow us to set a resolution value when we close the ticket?
I can get to "Issue Type Screen Scheme" and eventually can drill down into a screen titled "Configure Screen" - but at this point I'm not clear how to specifically remove fields from specific actions. I only see how to configure based on issue type.
Ideally - we would like to use the resolution value to keep tabs on tickets we are deferring or closing as won't fix, but we don't want issues to appear crossed out in our scrum backlog.
Yes. The issue type screen scheme tells JIRA what screens you want to use for Create, Edit and View actions separately.
You don't remove fields from actions, you remove them from the screens that are used when those actions are invoked.
The other place you might need to look into is the workflow. Each workflow transition can have a screen associated with it (and, of course, these can be totally different to the screen for create, edit or view). In your workflow you need to do two things:
An easy way to look at the workflow is to use the colours. If the status is blue or yellow, it's an "open" type status. If it's green, it's "ended"
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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