Mechanism to Prevent Duplicate Work Item when a Race Condition Occurs on Jira Connector

XMLWordPrintable

    • 3

      User Problem

      When user creates a work item that can be synced to Jira, such as Feature, there can be a race condition between IssueTimer and ContinuousPush and cause the work item to be duplicated in Jira Align (JA). Duplicate work items can cause confusion and double work for the collaborators of the work item.

      JA sends the POST API call to create the issue in Jira; the item is made, but the API takes time to reply. IssueTimer runs at the same time and sees the item created there; as the API hasn't replied yet, there is no mention on the DB that this item exists, so the IssueTimer creates it on JA as a duplicate. This is a scarce race condition between the two processes, as it depends on the fact that the timers will be hitting the same project in the exact second, while one is still finishing to create the issue while the other sees it as new.
       

      Suggested Solutions

      There should be a mechanism to prevent work item to be duplicated when the above situation occurs.

            Assignee:
            Andrew Zhang
            Reporter:
            Samuel Rompas
            Votes:
            12 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated: