Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-10548

Cloned issues inherit the Completed Sprint value and can't be removed

XMLWordPrintable

      Cloning issues that are with completed sprint value will inherit the value and can't be removed from UI.

      The cloned issues however won't show up in the completed sprint reports.

      Workaround 1

      Remove the sprint value from its field via JIRA issue navigator bulk edit:

      1. search for the affected issues in the Issue Navigator;
      2. click Tools > Bulk Edit;
      3. select the issue and click Next, then select Edit Issues and click Next;
      4. select Change Sprint and edit the value accordingly - if you don't want the issue to be associated with any sprints, leave the field empty;
      5. click Next and proceed with the instructions to complete the change.

      Workaround 2:

        1. screenshot-1.png
          0.2 kB
          Rob Haughey
        2. image-2016-07-22-13-20-14-058.png
          11 kB
          Silvi
        3. clone issue.jpg
          39 kB
          Sergii Sinelnychenko

            [JSWSERVER-10548] Cloned issues inherit the Completed Sprint value and can't be removed

            Sergii Sinelnychenko made changes -
            Attachment New: clone issue.jpg [ 495365 ]
            Sergii Sinelnychenko made changes -
            Resolution New: Not a bug [ 12 ]
            Status Original: Short Term Backlog [ 12074 ] New: Closed [ 6 ]

            Sergii Sinelnychenko added a comment -

            Dear Customers, thanks for your feedback on the issue so far, it's greatly appreciated. After a thorough evaluation of the reported issue, we have the following insights to share:

            • The inability to remove Sprint values from a completed Sprint is not considered a bug. This functionality has never been supported. However, if you believe there should be an option to modify Sprint data for completed Sprints, we encourage you to detailing your specific use case in this suggestion https://jira.atlassian.com/browse/JSWSERVER-26370
            • When cloning an issue, you have the option to either include or exclude Sprint data in the clone. Please refer to the attached screenshot for guidance on how this can be done. the feature is available in 10.3 LTS.
            • We have identified that cloned issues retaining Sprint data and appearing in Sprint reports is indeed an unintended behavior. This has been registered as a bug and tracked here: https://jira.atlassian.com/browse/JSWSERVER-26365.

            We appreciate your understanding and encourage any further suggestions or feedback you may have.

            Warm regards,

            Sergii Sinelnychenko
            Senior Software Engineer
            Atlassian

            Sergii Sinelnychenko added a comment - Dear Customers, thanks for your feedback on the issue so far, it's greatly appreciated. After a thorough evaluation of the reported issue, we have the following insights to share: The inability to remove Sprint values from a completed Sprint is not considered a bug. This functionality has never been supported. However, if you believe there should be an option to modify Sprint data for completed Sprints, we encourage you to detailing your specific use case in this suggestion https://jira.atlassian.com/browse/JSWSERVER-26370 When cloning an issue, you have the option to either include or exclude Sprint data in the clone. Please refer to the attached screenshot for guidance on how this can be done. the feature is available in 10.3 LTS . We have identified that cloned issues retaining Sprint data and appearing in Sprint reports is indeed an unintended behavior. This has been registered as a bug and tracked here: https://jira.atlassian.com/browse/JSWSERVER-26365 . We appreciate your understanding and encourage any further suggestions or feedback you may have. Warm regards, Sergii Sinelnychenko Senior Software Engineer Atlassian
            Sergii Sinelnychenko made changes -
            Link New: This issue has a derivative of JSWSERVER-26365 [ JSWSERVER-26365 ]
            SET Analytics Bot made changes -
            Support reference count Original: 18 New: 19
            John Chin made changes -
            Affects Version/s New: 9.12.11 [ 108610 ]
            Marcin Sasinowski made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 1002574 ]
            SET Analytics Bot made changes -
            UIS Original: 17 New: 16
            SET Analytics Bot made changes -
            UIS Original: 34 New: 17
            SET Analytics Bot made changes -
            UIS Original: 33 New: 34

              Unassigned Unassigned
              mfahd Fahd
              Affected customers:
              143 This affects my team
              Watchers:
              106 Start watching this issue

                Created:
                Updated:
                Resolved: