How to count story points when moving tasks to resolved status instead of done

Other Questions Jira
1

I’m working with a development team using scrum methodology and need to adjust our Jira setup. Our workflow has these stages:

  1. Backlog/To Do
  2. Active Development
  3. Complete/Testing Phase
  4. Finished/Delivered

Right now the burndown chart only updates when we move items to the final “Finished” column. But I want the story points to be counted earlier when tasks reach the “Complete/Testing” stage instead.

Our team considers work finished once developers complete their coding and run unit tests. At that point we want those story points reflected in our burndown progress rather than waiting for the final delivery step.

Is there a way to configure Jira so the burndown chart updates at an earlier workflow stage? I need the points to register as complete before the absolute final status.

2

totally feel u on this! we had the same issue. just head to ur board config, look for estimation settings, and change the ‘done’ column to the testing phase. since we did this, our velocity has been way better tracked - devs are usually done b4 QA starts testing.

3

To modify your burndown chart in Jira to recognize story points earlier, access your board settings and navigate to the Column Management section. Here, you should configure the mapping to ensure that the “Complete/Testing Phase” status is treated as “Done.” This allows the burndown chart to reflect completed story points as soon as coding and unit testing are done, improving your team’s visibility into progress during the sprint. This adjustment should take effect immediately and enhance your current sprint’s reporting.

4

To adjust your burndown chart in Jira, navigate to your Scrum board’s settings and find the “Columns” section. Here, you’ll want to modify your workflow mapping. Specifically, map your “Complete/Testing Phase” status to the “Done” column. This configuration will allow Jira to count story points as complete when tasks reach the testing phase, rather than waiting for full delivery. I’ve implemented this change for several teams, and it significantly enhances visibility on team progress during sprints.