I love how the children estimates roll up into the parent, but I see one problem with this. Let me describe:
ohhh noooesss!!! the parent's original estimate should not have been increased to 13h. It should remain at 8h since that's the final estimate before work began. so my question is this ...
how do you "lock" the original estimate at a certain point in the workflow?
Either sub-tasks rolls up its estimates or it does not. As common as it might be that people want to freeze the original estimate, it also common for people to not freeze the estimate. I would probably copy in a post-function the original esitimate to a custom field when switching into the in progress status.
If the issue enters and leaves the in-progress status and then enters in progess status again, the custom field would be set to the new estimated value.
I believe the JIRA Misc Workflow Extensions plugin provides the copy operation that you need to implement this solution.
i'm happy to say i already had both of those plugins installed. at this point, i'm trying to determine the best field type to provide this custom field. (Number seems obvious, but I'm on the prowl for something that perserves similar to original estimate -- as days, weeks, hours.)
sadly, no, norman. i've been racking my brain for days trying to find a solution. i even went so far as report it to Atlassian and to create another question. if you have any other nuggets of wisdom, i'm all ears. have a read.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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!
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