This is outcome of DoS investigation of https://support.atlassian.com/browse/GHS-18987

      Steps to reproduce

      1. ensure that You have 2 issue statuses that ID of the first one is prefix of the second one.
        eq. status11 that has id 11 and status111 that has id 111.
      2. create an agile board with those statuses configured.
      3. Move issue from the longer status id to the shorter status id. The dialog should be presented and trigger should be registered on 'a[href*='action=11'].issueaction-workflow-transition'
      4. now when You move issue from shorter status 11 to longer 111 another dialog will be created with trigger a[href*='action=111'].issueaction-workflow-transition and that trigger will be triggered. but the longer trigger "href*='action=111'" also satisfies the previous "href*='action=11'" so there will be 2 dialogs triggered (2 network operation) and incorrect dialog will be displayed.

      I think that there is an error in the file gh-InitDialogs.js

      trigger: 'a[href*="' + action[0] + '"].issueaction-workflow-transition',
      

      this selector makes possible to trigger multiple times (multiple forms).
      Or maybe the forms should be removed along with the triggers after closing.

            [JSWSERVER-12275] Issues don't transition to correct status in Agile Board

            There are no comments yet on this issue.

              Unassigned Unassigned
              tkanafa Tomasz Kanafa
              Affected customers:
              1 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated: