using jira 6.3.13 I'm trying to find a solution for the following problem.
There is this rather complex software development workflow which is containing pool-statuses for issues after passing through different stages. Pool status means basically that no one is assigned to the ticket at the moment. That is why during the last transition leading to this pool status the current assignee is deleted.
But pool statuses can be skipped automatically by the use of listeners. If all the conditions are met that is. If not, the ticket just remains in the pool status and needs to be edited and afterwards transitioned manually.
Now the problem: a new requirement is, that only the current assignee can edit and transition an issue - no one else. If this is implemented by reducing the projects permissions for editing and transitioning issues only to the current assignee, the auto-transition won't work anymore. This is, because the "to be skipped" pool status has no user (especially not the user trying to carry out the transition) assigned.
Any thoughts on how this could be solved?
Thanks in advance
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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