Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-10170

Improve concurrency handling in JIRA

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Do
    • None
    • Bulk Operations
    • None
    • We collect Jira 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.

    Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Currently there are a few multi-stage processes in JIRA where someone can modify the underlying issue whilst the process is still being completed (workflow migration, bulk move, bulk edit).

      We need a way of implementing optimistic concurrency in JIRA. Perhaps a revision id on the issue table that gets incremented with each change?

      Attachments

        Issue Links

          is related to

          Suggestion - JRASERVER-11382 Remote API concurrency issue

          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-13263 IssueNotFoundException is thrown right out to the user if a workflow action is taken on a deleted issue

          • Medium - Medium priority issues
          • Closed

          Suggestion - JRACLOUD-10170 Improve concurrency handling in JIRA

          • Closed

          Suggestion - JRASERVER-1917 Control Concurrency for Update Functions in JIRA

          • Closed

          Activity

            People

              anton@atlassian.com AntonA
              scott@atlassian.com Scott Farquhar
              Votes:
              10 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: