We have about 12 users on our team. JIRA issues are first assigned to our team id. Then individual team members click the "assign to me" link to take ownership of the ticket and work the ticket until closed. The issue I have is that sometimes other team members within a few seconds accidentally assign the same issue to themselves that I've already assigned to myself because they have a stale view of the ticket assignee. I also try to prevent taking tickets that other team members that have already assigned to themselves by reloading the JIRA page multiple times as a workaround (very tedious). Any way to create a rule that a ticket cannot change ownership more than once per minute, etc? Most code repositories have a way to checkout or lock a resource. Hoping there is a way to do this in JIRA.
I'm fine with the ticket being updated. The issue is just if the assignee changes. This could result it both team members performing the same task which can just waste time or potentially cause an outage if for example two people try to reboot the same host. Hopefully it can be added as a feature in in a future JIRA release.
This has happened to my team and there's nothing much that can be done on tool side. The workaround I can think of is that you can hide the native "Assign" button via the Permission scheme then just create a transition "Assign to Me" which has an "Assignee" field which will transition it to the "Assigned" status. Once in this status, there's no way to reassign the ticket other than putting it back to "Open" or something like "Unassigned" which can be restricted via the Workflow Scheme.
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