Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-1224

App migration listener-triggered is sometimes sent before onStartAppMigration() is called

XMLWordPrintable

    • Severity 3 - Minor

      Issue Summary

      Currently the App migration platform sends the event listener-triggered when the transfer is created, not when the listener is actually triggered in server.

      Those two things happen very close to each other.

      However, if Jira/Confluence has trouble triggering the job that will kick onStartMigration(), the Connect app may receive an event for something that is still about to happen or might not happen due to server error.

      Steps to Reproduce

      This is quite difficult to reproduce from a customer point of view. It required debugging the app migration code in the Cloud Migration Assistant and putting break points in the code where the listeners are called.

      Expected Results

      listener-triggered is called after onStartMigration()

      Actual Results

      The symptoms vary. generally, REST calls receive a HTTP 400 or HTTP 403.

      Workaround

      The only work arounds are

      • to make the Connect app code pause when receiving a listener-triggered event
      • to retry on the HTTP 400

            [MIG-1224] App migration listener-triggered is sometimes sent before onStartAppMigration() is called

            Callum Bundy added a comment -

            Fixed and released in current CMAs

            Callum Bundy added a comment - Fixed and released in current CMAs

              Unassigned Unassigned
              jrichards@atlassian.com James Richards
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: