When a record is reopened it gets assigned to the person who reopened it.
Is it possible to enforce roles so that if the record is reopened it stays assigned to the original person like the Developer listed in the Roles tab? It appears if a person reopens record they are assigned to it. We want to be able to Reopen to Developer who was assigned it originally
Here is the Transition in the workflow. Only see this : Fire a Issue Assigned event that can be processed by the listeners.
|All||Conditions (0)||Validators (0)||Post Functions (6)|
There are no conditions on this transition.
No input parameters checks will be done before this transition is executed.
Set issue status to the linked status of the destination workflow step.
Add a comment to an issue if one is entered during a transition.
Update change history for an issue and store the issue in the database.
The Resolution of the issue will be cleared.
Re-index an issue to keep indexes in sync with the database.
Fire a Issue Assigned event that can be processed by the listeners.
When a record is reopened it gets assigned to the person who reopened it
This should not happen based on your workflow. If it does, then you should raise a support request.
We want to be able to Reopen to Developer who was assigned it originally
This may require you to create a custom post function. Have not come across any post function that does this. Maybe if you search around, you'll find one.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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