We are using JIRA Version: 6.3.10 with Service Desk plugin 2.3.6. We sometimes have multiple agents working the same queue, and occasionally run into a situation where two agents assign the same issue to themselves that they had both found to in unassigned status. Inside JIRA record it ends up being recorded as the first agent assigning an unasigned issue to himself, and the second agent changing assignee from the 1st agent to him or herself. This can cause duplication of effort that can be either a waste of time in best case, or has the potential to create a negative customer impact in worst case.
What are the best options that we could implement that might allow us to avoid this issue? For example, would it be possible to have a validation to confirm that issue is currently unassigned when using the "assign to me" link that would prevent using it if item is already assigned?
I am guessing this is a rare scenario where both agents do it at the same time (or else they wouldn't have found the issue as unassigned), right?
If so, the first agent should get notification when the assignee is changed by the second agent, right? Can you check if the notifications are configured correctly?
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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