Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Sprint Health Gadget: excluding "cancelled" issues / best practices

Hi Community :)

The Sprint Health Gadget counts all story points in the sprint. However, some stories end up being "cancelled" yet have story points on them (for example, these stories get another resolution value than "Done") that get counted in the green (Issues Done) part:


For example, in the picture above I have 3 "cancelled" stories with the resolution value "Won't do" that have a total of 8 points. So the 24 points green bar is inflated by 8 points. I guess one way to tackle this is to remove the story points from "cancelled" stories...

I'd like your input. How are you guys excluding those "cancelled" stories from the green bar tally?


1 answer

1 accepted

2 votes
Answer accepted
Mark Segall Community Leader Jun 06, 2022

Hi @Kristján Mathiesen and welcome to the community!

Just one man's take... I typically don't worry about canceled issues as they usually lead to an uptick in velocity for that sprint because the team will typically be able to bring in more work as a result.  This can all be explained away during retro.

I would also say that this should be treated as an exception case.  If you're canceling issues frequently, you probably need to re-evaluate your sprint planning process to see if there is opportunity to catch cancelations before starting the sprint.

Hi @Kristján Mathiesen -- Welcome to the Atlassian Community!

Yes, what Mark suggested...

What does "cancelled" mean for the team.  For example, is it:

  • we agreed to do this feature, the stakeholders changed their mind, and now we are not doing it...or
  • we defined a goal, we met the goal, and there were a couple of "shiny" stories/sub-tasks that were not needed so we are not doing them (e.g. "stretch goals")...or
  • the PO cancelled this sprint due to large business need changes, and so the stories are no longer relevant...or
  • etc.

Such symptoms may be opportunities to learn and improve for backlog refinement and Sprint Planning.  And seem like good things to discuss for the team retrospective.

Kind regards,

Like Kristján Mathiesen likes this

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,767 views 37 47
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you