Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

My board's reports shows sprints from other boards, due to a task's sprint history.

haspero
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 8, 2026

Hello all,


I have a work item that recently moved to my team's board (X) from another team (Y). That work item had been in 2 active sprints while being on (Y), but was never resolved.

 

The problem is, these 2 sprints are now showing on (X)'s report list, which affects its velocity tracking report and definitely overpopulates its report list.

For more details:

  • My board/team (X) is new. Its report list should only show a test sprint I created and resolved before kicking off the team.
  • The two sprints existed before my team or my board (X) even existed.
  • (X)'s filter query is only tracking the project and its unique team field (ORDER BY rank)
  • (Y)'s board query tracks the assignee of this issue. However, removing it from (Y)'s query wouldn't resolve the issue.

 

Does anyone know how can I prevent JIRA from showing other team's sprints from the task's history?

Thank you very much!

4 answers

1 vote
haspero
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 13, 2026

Thank you very much guys! I think in the end I will go for the solution of moving that task back to the original team and close it. Feels like the problem is more on how we managed that task than in any JIRA setup :) 

0 votes
Stephen_Lugton
Community Champion
January 13, 2026

Hi @haspero 

I have in the past managed to clear out all of a work item's sprint history by mistake.

I think what I did was to use a filter that included the work item; in your case you could use:

Key = WorkItemKey

Then I think I checked the tickbox for the work item in the filter list and then did a bulk update from the more actions menu [...] at the top right, I then changed the sprint field value in the bulk update field list, for which you need to know the sprint ID not just the name.  You can find this by clicking on the sprint name in the filter list (you'll need sprint as a column), a filter box will open with a filter something like:

"cf[10008]" = 457

The number is what you need to use in the bulk update sprint value.

This is from memory as I don't want to wipe out the sprint details on one of my tickets testing this.

Note that doing this would remove any trace of that ticket being in Team Y's sprints.

Stephen_Lugton
Community Champion
January 13, 2026

This is probably a bug and may one day be fixed

0 votes
Iryna Komarnitska_SaaSJet_
Atlassian Partner
January 12, 2026

Hi @haspero ,

Unfortunately, there is nothing you can do about the work item history.

In your case, it would probably be better not to move the task, but to create a new one in the appropriate board and add it to the sprint.

 Also, if you are looking for a high-quality report to analyze your sprints, I can recommend an app developed by my team — Time in Status app.

db5dc529-5d1e-4e49-a121-412e2571ae35.png

One of its features is Sprint Report, which allows you to review the performance of your sprints from different perspectives.

We have also recently released the ability to analyze active sprints.

Group 23.png

 And soon you can expect an update — a detailed breakdown of each metric with a list of tasks based on which the indicators were calculated.

 I hope you find it useful!

 

0 votes
Deleted user
January 8, 2026

Hello @haspero 

In short, you cannot delete or 'erase' any Work Item's history as to what Sprints it previously has been in, because Sprint membership is tracked via the Sprint field, and every change to that field is written to the issue’s change history, and that history is immutable by design.

PS. Work Items can't be 'moved' between Boards, because Boards are just viewing portals that display Work Items based on a filter, that why a Work Item can appear on multiple Boards simultaneously. This has always been the case.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events