Our team is having issues where people keep accidentally taking over tickets that are already assigned to someone else. This happens pretty often and it’s causing confusion about who’s actually working on what. Is there any setting or plugin that can lock tickets once they’re assigned to a person? Or maybe something that shows a warning message when you try to change the assignee on a ticket that’s already been taken by someone else? We really need to find a solution because it’s messing up our workflow and people are stepping on each other’s toes without realizing it.
Start with your permission schemes - you probably have too many people with ‘Assign Issues’ permission. We cut it down to just project leads and managers, which fixed most of our accidental reassignments. For tickets already assigned, add post functions to your workflow transitions that block changes unless the current assignee makes them. There’s also a field config option that locks the assignee field after initial assignment (you’ll need admin access). Or set up automation rules to auto-reassign tickets back to the original person if someone changes them without approval - makes a good safety net.
the jira suite utilities plugin works great for field locking. i use the ‘behaviour’ feature to grey out assignee fields after someone’s assigned - stops most accidental changes. you can also tweak your screen schemes to hide the assignee field from certain user groups or project roles.
We had this exact problem and fixed it by tweaking our workflow. I modified the transition rules so users have to add a comment explaining why they’re reassigning someone else’s ticket. It creates a paper trail and makes people think twice before doing it. You can set this up using validators in the workflow editor - just make the comment field mandatory for reassignments. It’s not a hard lock, but we saw way fewer accidental reassignments after this. Also set up notifications so the original assignee gets alerted when their tickets get moved around. Helps catch issues fast.
This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.