-
Bug
-
Resolution: Not a bug
-
High (View bug fix roadmap)
-
None
-
6.3.9.2, 6.3.12, 6.3.13.0, 6.4.0.3, 7.0.0, 7.1.0, 7.2.0, 7.3.0, 7.4.0, 7.5.0, 7.6.0, 7.7.0, 7.8.0, 7.9.0, 7.10.0, 7.11.0, 8.5.0, 9.12.11
-
6.03
-
19
-
Severity 3 - Minor
-
16
-
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:
- search for the affected issues in the Issue Navigator;
- click Tools > Bulk Edit;
- select the issue and click Next, then select Edit Issues and click Next;
- 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;
- click Next and proceed with the instructions to complete the change.
Workaround 2:
- has a derivative of
-
-
- Gathering Impact
-
- is caused by
-
JSWSERVER-6541 Ability to clone an issue without cloning Agile sprint information
- Closed
-
- Closed
- derives
-
SW-3157 Failed to load
- was cloned as
-
COM-1116 Loading...
[JSWSERVER-10548] Cloned issues inherit the Completed Sprint value and can't be removed
86c315441630 - It's been over 10 years since this bug was first reported... Doesn't look like Atlassian is interested in fixing it.
I have found that cloning a single Story gives you the choice to include sprint values or not. But yeah, once the deed is done, there is no way to go back and clean it up. Haven't tried the bulk-edit workaround in a while, but it wasn't working 3 years ago when I tried it.
It would be very beneficial to my team if this bug were fixed.
This bug is affecting Easy Agile Programs customers who use issue cloning.
When planning team-level issues in the app, users select a series of Jira sprints for each Increment. This means that the app shows the issues from those sprints, and issues planned in Easy Agile Programs will be added to those sprints in Jira.
The app also maintains two custom fields for these issues based on these sprints.
Because cloned issues incorrectly receive sprint values, the app assumes that the issues should be in these sprints. It will show these cloned issues in the given sprints, and they'll also appear in JQL searches using the associated custom field.
Given the app uses sprints from Jira as a "single source of truth", we're unable to correctly handle cloned issues with incorrect sprint fields.
Thanks to the customer who was able to identify this bug as the root cause!
This is impacting our teams, please help to remove sprint information from Clone++
Hi, our org is using Jira cloud. The workaround does not work. Neither does creating a fresh clone and ensuring not to clone sprint values.
How can this possibly not be fixed after 9 (NINE) years!?!? if it's not possible, let us know, otherwise, please, you've got 114 reporting this, please take a look and fix. Thx.
I've just come across this with a few of mine. Users picked the wrong sprint, that sprint was closed. Now can't remove the completed sprint from the list, but it was never worked on there or meant to be included. Throws off the reports because of it, I just want to be able to clear the field, would even jump through hoops to do it, but nothing so far I've tried has worked.
Would be great to have a way to delete a sprint out of the completed sprints field for a given ticket.
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:
We appreciate your understanding and encourage any further suggestions or feedback you may have.
Warm regards,
Sergii Sinelnychenko
Senior Software Engineer
Atlassian