The problem appears on JIRA 7.2.7.
The design of this listeners configured to do simple actions, which can be tested independently and fixed quickly.
Bug: when listener A processes before listener B, then issue assigner don't change. Otherwise (autoassign after autotransition), both listeners work correctly.
It was founded that listeners form queue of work randomly and process consistently. The order of queue can be changed through the plugin reinstalling, listener updating or server restarting. It seems that java-code “event.getIssue()” returns current local issue state, so the listener B has old issue assigner after listener A actions and saves issue state B in database with old value.
Please answer following questions:
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot