automatically decrease remaining story point before issue completion

Hi there!

I am using JIRA Agile Simplified Workflow with 4 columns / status:

To do - In progress - To check - Done

The "To check" columns is used so that someone else has to quickly check the work before moving it to "Done". Of course, Done is the column with the 'set resolution' box.

I would like that the burndown chart reflects better the fact that when an issue is in the "To check" column, 80% of the issue is done. So if the issue is worth 10 story points, I would like to see it as 2 story points remaining once it hit the "To check" column

Is that possible?


PS: I am really impressed by JIRA / Confluence! So much possibilities, yet it is really intuitive, and I managed to configure it without hassle, and everytime I am looking to try new things with it. Congratulation Atlassians!

3 answers

Hey Christophe,


Glad to hear you're having such a good experience with Atlassian products.

Unfortunately it is not possible to reflect partial work on stories using story points. The exception to this case would be splitting stories in sub-tasks, and completing them would add the story points to the main task (story) and update the burndown chart as you would like (however, the subtasks would be completed).

Another alternative to achieve what you want is to configure estimation using time (Original Time Estimate) instead of story points. This way, after configuring the 'Time Tracking' option as 'Remaining Estimate and Time Spent' on the Board Estimation settings, once work is logged into an issue in progress, the burndown chart will be updated accordingly. You may find more details about how to change these settings on the following document:

Hope this helps!



Jose Raupp

Hi Jose,

Thanks for your answer, I will give the Original Time Estimate a try and see if it fits my workflow! I will report on that later.




I switched from story point to time tracking. Unfortunatly, it does not address my request, as time estimate have to be entered manually when a task moves across various stages.

Thank you anyway for your help!



Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

562 views 0 6
Read article

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