Hello everyone, I see there have been a lot of workarounds involving modifying the offending issue, which is not always possible or straightforward since it may involve another team's closed sprint, and you could damage their board while fixing the issue.

Instead of trying to fix the offending issue, I flipped my logic to fixing my board. 

I reconfigured my agile board's filter to exclude the sprint values which came from another project, here is an example:

(project = X AND Sprint not in (1234)) OR (project = X AND Sprint is EMPTY) ORDER BY Rank ASC

The first section of the filter before the OR statement searches for all issues in sprints except for the one that I want to exclude.

The second section includes the backlog. 

I hope this helps, as this issue is incredibly frustrating! Hopefully Atlassian can fix this bug soon so that we don't need to keep inventing new workarounds when they stop working!

In project B, it's listing the 2 Sprints with the same name "Sprint 1" and if we delete the started Sprint 1(this Sprint 1 we are started in Project A and in Project B Sprint 1 i am not started.) in Project B, it is also deleting the Sprint 1 from Project A.

Can you add the feature like moving issues should clear the Sprint values for upcoming Jira release. 

Interestingly, after renaming and changing the dates, the sprint was removed from the board. When I look in the db, the sprint it still stored in table AO_60DB71_SPRINT, but shows a NULL rapid_view_id. I didn't check this beforehand, but it looks like somehow the change I made resulted in the removal of this ID.

I'm seeing the same issue with a new sprint added to another sprint board after the ticket was moved. Is there a work around to remove this sprint from the new board? I see no option to delete the sprint. Alternatively, I guess I could just rename it and change the dates, but if that's the expectation, it's poor UX.

I'd like to suggest that the team identify this as a transition screen when moving a ticket from one project to another. At least allow the user to decide which sprint/sprints to put the ticket in when it will show up on multiple agile boards.

Those filters did not cross projects. Each filter includes only one project. I'll file a support ticket for help.

Hi Jeff,

There likely is some overlap in the filters each of those boards, that is, one of your board filters likely includes a project listed on the other board. The best case of action would be to isolate your board filters to exclusive projects to avoid any overlap and this symptom. If you file a ticket at support.atlassian.com with our great Support Engineers, they can help you sort this out if you need any extra help.

Peter, that might be true but the added sprint from the other project will remain in the sprint history of the project it was accidentally added to. If there is a way to get rid of that added sprint I can't figure out. Knowing how to do that would go a long way towards minimizing the impact of this.

Hi jeff.shea,

Yes, that issue will show up on the new board as in the same sprint. If you find it on its new board and remove it from sprint, it will disappear back to the backlog (or bump down to the backlog if you do so from Plan Mode).

I understand the workaround and that is the policy we implemented when we discovered this but it is easy to make this mistake and the impacts can be pretty severe. If you remove the task that was added to another project will that remove the linkage to the sprint from the old project? Alternatively, can you remove the moved task from the other projects sprint after the fact? Possibly this is easy to fix and we just didn't understand all of the implications of doing this kind of move.

Because Agile Boards are cross-project, they need to be able to display Sprints that span all issues (from multiple projects) that are displayed on that board.

To work around this, please remove the issue from the Sprint it is in before moving it to the new project. This can also be done after it is moved by looking at Plan Mode, right-clicking the issue, and choosing "Remove from Sprint".