-
Bug
-
Resolution: Fixed
-
Highest (View bug fix roadmap)
-
8.8.0, 8.13.3, 8.17.0
-
8.08
-
24
-
Severity 2 - Major
-
94
-
-
Summary
When moving a Jira issue from one project to another project, any completed Sprint that is in the Sprints field will be automatically deleted from the issue.
This bug happens regardless of the way the issue is moved:
- It happens if the issue is moved from the issue view screen (using the option More > Move)
- If also happens when bulk moving multiple issues to a new project, from the issue search page
The closed sprint will also be removed from the field if the issue is moved to another project from the More → Move option.
Note that the bug will not happen if the user is not allowed to edit the moved issues in the target project (more information about that in the notes section below).
Steps to Reproduce
- Create 2 project A and B
- Login as a user who is granted all the basic permissions (Edit issues, Move issues, Manage Sprints...) in both projects
- Create a sprint
- Create an issue and add it to the sprint
- Close the sprint and move open issues to backlog
- Open the issue in the issue view screen
- Click on the button More > Move, and move the issue to a new project
Expected Results
The closed sprint should not be deleted from the Sprints field.
Actual Results
The closed sprint is automatically deleted from the Sprints field.
When checking the history, we can see that this deletion happened automatically right after the move was completed, on behalf of the user who executed the move:
Workarounds
Suggestion 1
Make sure that the Sprint is active (or re-open it if it's already closed), before moving issues to a new project
Suggestion 2
If the Jira issues have already been moved and the completed Sprints were deleted, then you can re-add the completed Sprints to these issues either by using the CSV import functionality, or by using the bulk edit issue functionality,
Notes
Situation(s) where the bug does not occur
The bug will only occur if the user moving issues is allowed to edit issue in the target project. For example, in the 2 scenarios below, the bug will not occur, meaning that the completed sprints will not be removed from the Sprints field:
- Scenario 1: the user is not granted the Edit Issues permission in the target project
- Scenario 2: the user is not allowed to the edit the issue because of one of the status in a workflow that belongs to the target project is configured with the property jira.issue.editable set to false, and after the issue is moved, the issue lands in that status
Another impact of the bug
The Velocity Report loses the team velocity history
- is a regression of
-
-
- Gathering Impact
-
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Gathering Impact
-
- split to
-
-
- Gathering Impact
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
[JSWSERVER-13333] Moving Jira issues to a new project will automatically delete closed/completed sprints from the Sprints field
RE @Jamie Gerace's comment: I concur. What gives Atlassian team? If you're going to transfer the issue/ownership, you should transfer the votes & watchers too!!!
(Maybe Jira won't let the support team clone the voters & watchers? ... if that's true I believe it further underscores the need for Atlassian to fix this bug)
They didn't even link the two issues together. This issue has been open for 7 years, the new one a few months.
So you moved it from this ticket with many more affected customers to a new ticket with few affected customers, sketch.
Dear All,
The current issue :
When moving a Jira issue from one project to another - any completed Sprint that is in the Sprints field will be automatically deleted from the issue.
will be continued in this JAC ticket, please be informed that we are working on solving this issue
As this ticket was originally related to another issue - the initial report been opened under new JAC :
https://jira.atlassian.com/browse/JSWSERVER-21518
Issue details:
Bulk edit and of Sprint field and Bulk Move will remove issues from closed sprints
When a sprint is closed but it still have open issues, then the issues go back to backlog (or a new sprint). If an user tries editing the sprint field on one of these issues, he has the option to add a new value but he can't remove the closed sprint. When the sprint field is edited through 'Bulk Operation', the closed sprint is removed from the field and so a new value is added instead of keeping both.
If you experience this issue - please watch it under new JAC ticket
For a particular sprint, one can see the old/new sprint values in the Sprint Report details.
Assuming a set of issues has already been moved, how can the affected issues and the missing values be identified? I am not aware of a JQL option that identifies issues where the Sprint value changed, and even if you know that a change has occurred, how do you know what the old value was without going to every issue and recording the old values?
this is an absolutely fundamental problem, especially for calculating velocity 
Why was this reduced to medium priority? It's a bug that can ruin systems.
Dear All,
Let me explain why such changes were introduced to this ticket.
This ticket had been incorrectly defined, as it contained two separate problems. After conducting a comprehensive investigation of the ticket's history, it has been determined that migrating the Edit Sprints Field issue is the most appropriate course of action. This is how the ticket's history looks:
This is strong evidence that the ticket's high impact comes from the behavior associated with Issue Move operations. We apologize for any confusion caused by the previous misdefinition of the ticket. To address this, the original problem associated with Bulk Edit of Sprints Field has been moved to a new JAC ticket (https://jira.atlassian.com/browse/JSWSERVER-21518). I have also linked the tickets together to provide better visibility. If you have been affected by this problem, please add yourself as a watcher to the new JAC ticket.
We are also pleased to announce that the second problem associated with the Issue Move operations was resolved and the fix was released as a part of version 9.6.
Kind Regards,
Maria Mikolajczak
Jira Server Developer