-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
0
-
1
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Lot's of people, like us, need issue locking, even before Service Desk was created. And every time, this wasn't important enough.
Now with Service desk, this is ESSENTIAL!
Even with the Who's looking plugin, time is lost because hard working people try to solve the same issues, as fast as they can. Collision is inevitable.
So please, make this a priority.
The same goes for setting different default Viewable by, groups. Essential when you need to keep comments internal.
jan
- duplicates
-
JRASERVER-6146 Implement issue locking
- Gathering Interest
- relates to
-
JSDCLOUD-782 need for Issue locking, now more than ever
- Closed
Hi,
Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.
This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).
We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.
To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.
Regards,
Jira Service Management, Server & Data Center