GitHub data might be in inconsistent state in Jira due to timing issue

XMLWordPrintable

    • 1
    • Severity 3 - Minor

      Issue Summary

      With GitHub and Jira integration, data from GitHub is coming to Jira via Webhooks. In case there are two webhooks coming in around the same time, data in Jira might be in inconsistent state. E.g. PR is Merged in GitHub but Declined in Jira.

      As per GitHub docs, they send us updatedAt without milliseconds, which means if 2 webhooks are sent simultaneously, there's no way for us to determine which one to consider as first. Even if GH becomes more consistent (e.g. sending first webhook as OPENED, not DECLINED), we will ignore the 2nd one and it will remain "Open" forever. 

      Steps to Reproduce

      Not always reproducible. For knows instance, in the same setup it is working fine in 95% of time.

      1. Have GitHub integration with Jira via App.
      2. Open and Merge PR in GitHib (using script with no break between open in Merge)

      Expected Results

      Latest webhook is being considered and Jira reflects correct status of object in GitHub.

      Actual Results

      Inconsistent status of objects in Jira. E.g. PR is Merged in GitHub but Declined in Jira.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              Assignee:
              Unassigned
              Reporter:
              Andrey Lazarev
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: