We need the ability to estimate each subtask in an issue and have those estimates roll up to the issue. And when we enter time on any subtask, we want the time entered to reduce the amount of remaining estimate on the subtask, and in turn adjust the remaining time on the issue. So far with Tempo, it seems like the issue is ignored and everything rolls up to the project level. Because of the way we bill time both internally and externally to our customers, the billable unit of work is the issue and the granularity of the work is the subtask. It's nice to know what the total hours are on a project but the customer is far more concerned with the individual issue. Have we discovered a limitation with Tempo, or are we just not understanding how this all works? Any advice or help you can provide would be appreciated. Thank you.
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