• Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • Issue View
    • None
    • 0
    • 1
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      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

            [JSDSERVER-782] need for Issue locking, now more than ever

            Atlassian Update – 19 Feb 2021

            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

            Charlie Marriott added a comment - Atlassian Update – 19 Feb 2021 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

            JonasC added a comment -

            Hi there,

            here's my attempt at solving this problem.

            I have developed a plugin called JIRA Issue Lock. You can find the Marketplace page here: https://marketplace.atlassian.com/plugins/net.koncis.atlassian.jira-issue-edit-lock

            Users with edit-rights can lock down an issue for edit when viewing an issue, and while that happens, no other user can edit the issue. The user releases the edit-rights when he browses eg. to another issue/page (timeout is default 30 seconds but can be configurated. This means he has 30 seconds to jump back to the issue to avoid loosing the lock).

            The plugin is configurated on a per-project basis, and configuration also includes "Admins-override lock" and "auto acquire lock when viewing issue".

            JIRA versions supported are 6.2.X-6.4.X and 7.0.0-7.0.3, and it should work all over in the Service-desk and Agile parts.

            If you have any ideas for improving the product or use an earlier version of JIRA, just let me know, and I'll see what I can do.

            JonasC added a comment - Hi there, here's my attempt at solving this problem. I have developed a plugin called JIRA Issue Lock. You can find the Marketplace page here: https://marketplace.atlassian.com/plugins/net.koncis.atlassian.jira-issue-edit-lock Users with edit-rights can lock down an issue for edit when viewing an issue, and while that happens, no other user can edit the issue. The user releases the edit-rights when he browses eg. to another issue/page (timeout is default 30 seconds but can be configurated. This means he has 30 seconds to jump back to the issue to avoid loosing the lock). The plugin is configurated on a per-project basis, and configuration also includes "Admins-override lock" and "auto acquire lock when viewing issue". JIRA versions supported are 6.2.X-6.4.X and 7.0.0-7.0.3, and it should work all over in the Service-desk and Agile parts. If you have any ideas for improving the product or use an earlier version of JIRA, just let me know, and I'll see what I can do.

              Unassigned Unassigned
              9cb130dade9f Jan Cornelissen
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: