Why would anyone consider them completed or want a report including them with issues actually worked and completed?
Hello @Greg Mueller
Cancelled issues show up in the report because Jira groups issues by Status Category. Those Status Categories are:
To Do
In Progress
Done
Every specific Status value belongs to one of those categories. Status values are customizable to have any name. Jira doesn't have native functionality based on Status value names, but rather based on Status Categories (plus, in some cases, whether or not a value has been added to the Resolution field).
As you can see, there is no special distinction for "cancelled" at the Status Category level, so Jira has no special functionality to apply when the status of an issue is "Cancelled".
Ok, so that begs the question, what do people typically do with cancelled items? How do they track those ? This need has to be common to every team who uses Jira.
Hi @Greg Mueller
Yes, and...to Trudy's ideas, and as an answer to your question, "what do people typically do with cancelled items":
It depends upon the team and org.
Let's say a team has a Cancelled status, and they want those items not to be reported upon. The board filter could be updated to exclude Cancelled status, and so when something moves to Cancelled it is not reported upon...for some things.
They could instead intentionally remove the item from a sprint to show the scope change, and then abandon the item.
Others may note that some work happened before an item was Cancelled. In that case, they may leave the item as is in the sprint, but perhaps first alter its estimation value to reflect delivery was halted.
Kind regards,Bill
Thanks Bill!
On another thread, I was told that updating story points mid-sprint wont change sprint scope on the report... but will it?
It looks like you're new here. Sign in or register to get started.
