Post Function Set Story Points to 0 Does not affect Report

[Drew Bradford]

In our workflow we have the concept of Waived issues. Issues we decided we don't want or need to do anymore. For sprints I track Waived issues differently than closed or removed issues.

I've been trying to come up with a way to easily see if an issue is waived instead of closed/approved/completed. Currently when I look at the Burndown report Waived issues look exactly like Resolved issues and I need to click on each resolved issue to check the status and see if it's in fact, waived.

I've tried setting the story points to 0 in a post function when the issue transitions to waived but that does not affect the report. Eventhough the issue shows that the story points are 0, the report shows the original story point value and "Issue completed".

I could move the story out of the sprint before waiving it, again using a post function, but then the story would look like any other story that was moved out and not waived.

Is there any reason the following post function does not set the story points to 0 before transitioning the issue and setting it's resolution... or why isn't that picked up by the burndown report?

[Trudy Claspill]

Hello @Drew Bradford 

Can you provide images of your Burndown report to help illustrate the points you are making and explain more about how you would like it to appear differently?

[Drew Bradford]

Sure Trudy:

I would expect the second to right column to be 0 for the Waived issue instead of showing 3 story points since the Story Points were set to 0 before the issue was resolved. Clicking on the Waived issue shows the status of Waived and the Story Points are 0 but on the burndown report the story points remain what they were prior to the transition.

[Trudy Claspill]

The purpose of that column and the one to the left of it is to show the change in the estimate (story points) in the sprint during the execution of the action on that same line.

When the action is only a change in the Story points value you would see a Scope Change entry.

Because the story point change is happening in the same change with the issue transitioning to "complete" there is no separate entry. The burndown chart has to account for the decrease in story points during the activity, so it shows the decrement in points

If you want to see the scope change separate from the status change in the burndown you will have to change the story points and save that change prior to executing the transition. If there are only a few of you that use this Waive transition you could create a Manual Trigger Automation Rule. When triggered it could first change the story points to 0, then re-fetch the issue, then transition it to Waived.

This built in chart is not customizable. If you want a more customizable version of burndown charts I think you will have to consider third party apps.

[Drew Bradford]

That's a very helpful answer. Thank you.

I guess that I would also expect the story points change to be reflected on the report the same as if I manually changed the value. So if I change the story points to 0 and then waive it, it will show the decrease and then the completion. I could use that scenario to let off of on my external spreadsheet that I'm using. But since it doesn't record the story points change until after the transition I have to remember to change the points before I waive it.