We want to set up a story as a time bank and allocate sub-tasks to the story so that time logged against the sub-tasks uses up the time bank until there is no time left. At the moment when a sub-task is added then its estimated time is added to the estimated time of the story so we have to manually adjust the remaining time.
Thank you for your comments Tanner. Sadly the solution is not that simple. We want the time taken for the sub tasks to be logged against the story, so the "Include sub-tasks" check box needs to be ticked. We don't want the Estimated time on the story to be changed whenever a sub-task has time logged against it.
To put it another way, when we set up the story, we want to fix the estimated time at say 100 hours. Then we carry out a sub-task that takes 20 hours, so we want the logged time on the story to show 20 hours, the Estimated time to still show 100 hours and the remaining time to show 80 hours.
ahh ... i see. then here's a possible solution:
of course, you'll have to write that custom code. you can do so with script runner. great plugin, and i use it often.
Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :). In the spirit of this month's august-challenge, we're sourcing stories of Jira Service Desk activation fro...
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