Uploaded image for project: 'Analytics'
  1. Analytics
  2. ANALYTICS-177

Sprint information for cloned issues is not correct in Sprint history table

XMLWordPrintable

    • Severity 3 - Minor

      Issue Summary

      In the case of a cloned issue, the Sprint ID value in the Issue sprint history are concatenated as a single string instead of these sprint IDs being listed individually. Cloned issues that have been added to only one sprint will be unaffected and have data in the Issue sprint history table.

      Steps to Reproduce

      1. Create an issue and add it to sprints.
      2. Clone the issue and choose to Clone sprint value as the issue is being cloned. 

      Expected Results

      The cloned issue should have each sprint added individually.

      Actual Results

      The sprint values are concatenated into a single field.

      Workaround

      Two potential workarounds are available:

      1. Use the last part of the sprint ID to get the sprint using sprint_ref.
      2. Clone the issue but choose not to clone the sprint value during the initial clone step. Once the cloned issue is created, add the new issue to your desired sprint(s). This allows the sprint information to be properly recorded for the cloned issue. 

              tling@atlassian.com Tina Ling
              bkiely@atlassian.com Brennan Kiely
              Votes:
              7 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: