Steps to reproduce:
Actual Result: Issue is in an Open state with resolution set (e.g. OPEN fixed)
Expected Result: Resolution is reset/purged.
How can I force the reset of resolution in the workflow?
I tried to reset in the POST Function of the target workflow to no avail.
I'm afraid you need to push the issue through a transition that clears the resolution. When you move an issue into another project, that really is all it does. It checks the config for incompatibilities and makes the minimal changes required, then moves it, with existing data.
I have tried it even in different positions without success:
before issue create
Transition: Create Post Functions The following will be processed after the transition occurs The contents of the field Resolution will be purged. Creates the issue originally. Re-index an issue to keep indexes in sync with the database. Fire a Vorgang erstellt event that can be processed by the listeners.
after issue create
Creates the issue originally. The contents of the field Resolution will be purged. Re-index an issue to keep indexes in sync with the database. Fire a Vorgang erstellt event that can be processed by the listeners.
If it is always going to the 'open' status put a transition that clears the resolution field the only an administrator (JIRA or Project) can execute that goes back to Open. You do realize by resolving the issue in one project and moving and reopening in another your created vs resolved reports won't be correct?
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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