We have a scenario for logging issues after they are resolved and I am trying to keep this process as simple as possible.
I have a workflow where the item is created in the "Closed" status and all that is required is a summary and a description (and the project of course). However, when adding a post-function to set the Resolution, i am still getting all issues in "Unresolved" state. Is this documented as the expect behavior because the transition is the "Create" transition?
As we are hosted onDemand, there is no access to scripting to work around this issue.
Thank you for any insight or input
Upon further research, I stumbled upon this paragraph in the documentation:
Which specifies that in order to set the Resolution during the "create" transition, you must add an extra post function AFTER your "Update Issue Field" post function for the Resolution field. That extra post-function is "Store Issue".
I have succesfully implemented this in our workflow and it works as advertised.
Yes, it probably is the post-function, it behaves oddly on "create"
Would it be possible to simply add the resolution field to the "create" screen for these scenarios - Jira always sets a resolution if you put it on screen, so it would work (especially if you set the default appropriately)
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
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