Forums

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

Duplication of data while using two D gadget

Balakumar
August 5, 2026

when a user story is moved from one sprint to another and in the Latest sprint it is marked as "done" but this is showing in both the sprints as duplicate in 2 D gadget with status as "Done". How to resolve this issue?

1 answer

0 votes
Walter Buggenhout
Community Champion
August 5, 2026

Hi @Balakumar,

There is no immediate solution to this. The @2D gadget displays work items based on real time data. The work item from your example has effectively been in 2 sprints (one where it wasn't completed and one where it actually was), but it only has 1 (current) status: Done.

Since the 2D gadget uses the current information of the work item, it is not capable of displaying the historical status from the work item in the previous sprint. That is simply a limitation of the gadget.

If you are looking to display the last status of the work item in the previous sprint somehow, you would need to look into a reporting solutions that is capable of using the history data from Jira in reports, which points towards a BI reporting solution.

Hope this helps! 

Balakumar
August 5, 2026

The user story is showing up in both the sprints but it has to show only in the current sprint alone.

Marc -Devoteam-
Community Champion
August 5, 2026

Hi @Balakumar 

This is explained by @Walter Buggenhout 

This is the way this works the issue has been part of multiple sprints.

Otherwise you have to re-open the old sprint and remove the issues from that Sprint, but then you lose that it was part of this Sprint and this could be couterproductive

Walter Buggenhout
Community Champion
August 5, 2026

Indeed. If you want your unfinished work items from a sprint not to show up in your sprint report, you'll have to remove them from the sprint before you close it.

However, that may look nice in your 2D chart, but it creates overhead in your actual work and does not make it easier to understand why you actually overcommitted your sprint initially (you'll need to dig deep in other reports to understand which items were added and/or removed from sprints).

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events