• Community
  • Products
  • Jira
  • Questions
  • How can we exclude stories closed with resolution "Won't Fix", "Duplicated", "Not Reproducible" and "Incompleted" out of Scrum Board's Velocity and Sprint Report , or Agile Classic's chart board?

How can we exclude stories closed with resolution "Won't Fix", "Duplicated", "Not Reproducible" and "Incompleted" out of Scrum Board's Velocity and Sprint Report , or Agile Classic's chart board?

I think those kind of issues shouldn't be reflected in sprint report as they're invalid. However, I cannot find how I can exclude them from the Scrum or Classic boards.

For example, Sprint report in sprint-h2 in the capture include a 10-point story which was closed with resolution "won't fix" but it's still counted in sprint report.

Can anyone help give suggestion on this? Thank you very much for your help in advance.

Cheers,

Jenjira

3 answers

1 accepted

This widget could not be displayed.

You can always try to exclude stories with those resolutions from the board filters. I don't know ifthat will help.

Best regards,

Peter

Oh, yes :). Thank you very much for the suggestion.

Hi again, Peter. I have tried changing the filter to exclude those cancelled issues. However, I found that velocity chart will throw "No issues present in sprint to generate scope change model" error if that cancelled issues used to be chosen to "Remove from sprint". This stop Velocity board from generating the result. Do you know how can we manage this issue?

Jenjira, this problem is caused by the fact that if you exclude these issue certain of your last sprints don't have any issues at all in them. See here for similar problems : https://jira.atlassian.com/browse/GHS-7250.

You might be able to change your filter back so that there is a least one issue in each sprint. As the velocity board only shows the last 7 sprints (as described here : https://confluence.atlassian.com/display/AGILE/Viewing+the+Velocity+Chart?focusedCommentId=317950207#comment-317950207 ) it should work again in a couple of sprints.

Best regards,

Peter

I see.. Thank you very much for the information :).

This widget could not be displayed.

Add a "Resolved Not Done" column to your board. Move it to the left of the Done column, so that the Done column retains the green (indicating "Done") horizontal rule, and the "Resolved Not Done" column's horizontal rule is yellow (indicating "In Progress").

Then the Velocity Report and Sprint Report will treat issues in Resolved Not Done as not completed, and the issues in the Done column as completed.

See also the similar question: How to exclude "Won`t Fix" user story from completed Sprint and its points from velocity chart ?

@Matt McClure. not following how adding a new resolution type "Resolved Not Done" helps as changing the resolution has no effect on the velocity report. When you speak about horizontal rules are you referring to swim lanes on the scrum board?

Please can you explain in more detail how your workaround works.

@Tom Corcoran

 

Velocity and Sprint reports are calculated per JIRA Agile Board.

For an issue to be added to the "done" sum of Velocity/Sprint, its status must be mapped to the last (rightmost) column on the Agile Board.

Nothing else has no influence on the math of a velocity report. Issue status doesn't matter (if status is a "To Do" or a "In Progress" or a "Done" category status); resolution not empty doesn't matter., etc., It's all about status mapping to the last column on the board.

Now, this can lead to some interesting problems... for example you have more than one board that includes an issue and the Agile Board column mappings across boards are the not the same. As a result, the Sprint report for each board will be different.

(don't worry about the horizontal rules / colors of the columns... not relevant)


@Dashboard User interesting, so it does not matter what the resolution field is set to just don't have the issue in the far right column to not be included in the velocity. I'll have to try that!

Surprised me too, and counterintuitive.

But experimentation has proven it to be true.

My use case it the opposite... dev-complete at the end of the sprint, and it get's thrown over the wall to end to end testing for confirmation.

Development team's work gets counted towards sprint velocity, per DEVS "internal" DoD.

This widget could not be displayed.

Just to support the already provided answer -  the below JQL did the job for me:

project = X AND issuetype in (Bug, Feature, Story) AND resolution in (Unresolved, Complete, Fixed)  ORDER BY Rank ASC

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

290 views 5 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you