In JIRA Portfolio, can Epics\Story estimates be setup to span the life of a release?
Say for example, I have a fixed release that is 3 months long and I have a Story underneath an Epic that is estimated at 100 hours and this story can be started at the beginning of the project. However, I don't want the story completed in the first hundred hours of the project. The resource will not work on it full time for 2.5 weeks. I would like the estimate to be spread evenly across the 3 month project release instead of upfront.
Can this scenario be setup in JIRA? In practical terms, I'm trying to figure out how to estimate for a Project Managers time on a project. With my current setup in JIRA Portfolio is shows her planned capacity only for the first 2.5 weeks and I would like to spread the 100 hour estimate across the duration of the release.
I'm also interested in some kind of feature to enable a slower burn down on certain issues. The only way that I know for handling this is to break that story apart into smaller tasks and schedule those tasks out across time by manually setting the "Earliest Start Date" on the smaller tasks. That's a lot of work for the project manager.
If there is a better way then I would love to learn how to do it. And if not, then a new feature for slowing the burndown on issues would be helpful.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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