Dashboard Filtering Issue when issue is spilled across multiple sprints

[Arjun S Raj]

Scenario:

I have created a dashboard to track the testing progress of my team and have a Rich filter- 2D gadget to show the defects count grouped by sprint & status.

Problem Statement:

As per our projects configuration, when an issue is spilled over from previous sprint, it will have multiple sprint values. - one of the completed sprint (which cannot be edited/removed) and other of the sprint to which it is moved to. 

Due to this, when bugs are filtered based on sprints, it appears under both sprints and hence causes duplicate values to be shown in the dashboard.

Is there a solution to this issue? (I have tried the possibility of using any other fields other than 'Sprint' to track the sprint value, but that doesn't look feasible)

[Nic Brough -Adaptavist-]

There is no problem here - your dashboard is accurately showing you that an issue was handled in multiple sprints.

What exactly is wrong with this?  What do you want your reports to actually tell you?

[Arjun S Raj]

@Nic Brough -Adaptavist-  Thanks for your reply. However the intention of my dashboard is to have a view of the count of issues. It doesn't matter whether it was handled in single or multiple sprints. I want the issue to appear only under the sprint in which it was closed or the latest sprint to which it is assigned to.

current dashboard display doesn't satisfy my requirement.

[Nic Brough -Adaptavist-]

Mmm, so you want your reports to lie to your users?  Is that really a good report?

[Arjun S Raj]

@Nic Brough -Adaptavist-  There is no matter of lying here . The report just doesn't show the information as per my requirement. Request  you to suggest a solution if you have any.

---

[Nic Brough -Adaptavist-]

No, you have explicitly stated that you want to lie about whether an issue was in a sprint or not.

Could you explain what report you actually want to get here?  If it's a useful one, it won't need to lie about the issue and sprint data.

[Arjun S Raj]

@Nic Brough -Adaptavist- 

What I want : I need a dashboard to show the count of issues in my project sprint wise. If an issue is spilled across multiple sprints, that should be shown only under the sprint in which it is completed (if the issue is closed) or under the latest sprint in which it is assigned (if the issue is not closed).

Why I Want this: Requirement is specific to the project and I think we do not need to have a detailed discussion on this here. 

How I can accomplish this: That is what I am looking for a solution. Please suggest if you have any.

[Nic Brough -Adaptavist-]

That's no problem, just search for "sprint = x".  It doesn't matter to your report if an issue has been in more than one sprint (unless it was closed in one sprint, reopened, and then closed in another, in which case, your report should be showing it)

[Arjun S Raj]

 I already have this filter and It doesn't work the way you've mentioned. Please see the below snapshot. This is how my dashboard currently looks like.  Here the data seems weird as the total count is not matching with the sum of individual sprint values. This is because some of the issues are part of  both the sprints and the grand total field is showing the unique issue count. 

In this case, 5 issues were spilled over from Sprint 2 to Sprint 3 and these are being counted under both sprints, which I definitely need to avoid.

Instead of the above, I would like to see the data as below, which makes way more sense to everyone looking at it.

	Closed	Total
Sprint 2	7	7
Sprint 3	6	6
Total	13	13

[Nic Brough -Adaptavist-]

No, that report would be inaccurate and hence lying to your users.  The gadget you show working is accurate, there's nothing wrong with it.

[Arjun S Raj]

@Nic Brough -Adaptavist- As I have mentioned multiple times, this is my requirement. Is it accurate or not  - I am not concerned about it at the moment.

please share your views whether it is feasible or not.

I am not interested in further discussions about whether it is accurate or lying to the users etc..