Jira tempo for Team tasks

Let's say we are building a new feature for a customer application. We set up a design task that should gather 3 specialists for 4 hours to discuss design approaches, comment on the use case and agree on a draft spec. What is the suggested approach for Tempo? One task, 12 hour estimate? 3 subtasks, one per user, all looking the same? Other? Please advise as this is quite coomon in our product design process. Thank you

1 answer

1 accepted

0 votes
Answer accepted

Hi Luis,

Create only one issue for this with a time estimate of 12 hours. All users log on this issue and you avoid endless duplicates. This makes it easy to follow up on worklogs, comments and decisions taken.

Logging on subtasks is useful if you have a big design task that you have split up into smaller units.

Kind regards,


Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Opsgenie

Getting the Most out of Atlassian and Opsgenie Together

We’re excited to invite you to this action-packed webinar where we will demonstrate how to integrate Opsgenie’s powerful alerting and on-call management tools with your entire Atlassian stack. Mar...

21 views 0 0
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you