It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
Issue 1
Subtask 1
Subtask 2
Subtask 3
Issue 2
Subtask 1
Subtask 2
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.
Hello Yousef,
Unfortunately I have not received an answer and it doesn't seem possible to do this in Tempo. We are currently looking at other solutions that better fit our business model.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.
Read moreHi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.