Can we lock a story's Original Estimate, so new subtasks only impact the Remaining work? Edited

I've seen a lot of similar questions, but not exactly this scenario.

We believe we're following the right guidelines by only estimating time in a Story's sub-tasks, and using the built-in rollup functionality to show all the work remaining for a Story.

However, once we set a Story in motion, it's possible that more subtasks could be discovered, and we'll add them to the story.

The issue is that adding these subtasks, with their time estimates, increases the original estimate roll-up of the parent story. So we aren't shown intuitively that the parent's estimate increased from its original value. Presumably it will show as a bump in that sprint's burndown, but not when looking at the story card itself. It looks like the estimate was always at that higher number. 

This is a bit different than having your Original estimate for an item, logging work to it, and also saying that now I think there's more work left than originally estimated. That will show nicely in the Time Tracking bars for the individual item; the Remaining will creep out past the Original.

What I'm asking is, is there a way to "lock" the Original Estimate of a parent story, so that when a new sub-task is added to that story, its estimates only impact the Remaining values of the parent story. The Original Estimate should stay the same, so that it's clear that more work was discovered than originally estimated,

1 comment

Anton Chemlev Community Champion Nov 27, 2017

Do you have ScriptRunner? If yes, you can create custom field and fill it on some transition or event.

If I'm understanding you correctly, you're suggesting to create a new field that the Original Estimate can be copied to in the event that something changes it?

Anton Chemlev Community Champion Nov 30, 2017

Yes, you are right. You will be able to capture initial Original estimate.

For example, you have Estimation step in your workflow. Make post-function on transition from this step, which will copy Original estimate to custom field. See ScriptRunner docs for additional info.

Comment

Log in or Join to comment
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,914 views 12 18
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot