How can I set a rule so that when you set time tracking and original estimate in sub-tasks and tasks

[Roman Mural]

Hello! My name is Roman.

I have a few important questions, I would be grateful for useful answers.

1) How can we configure Jira Cloud, or create some rule for task types, so that when we fill in the fields: original estimate and time tracking in tasks and subtasks, epic automatically summarizes this time?

2) Maybe you know the best way to track time to see the workload of each employee in Jira, to see the planned time, the actual time spent on a particular task?

3) How do people usually track and estimate their time in Jira?

4) How to track, for example, some short operational small tasks in Jira?

5) Why when you track sub-tasks in a task, the task automatically adds all the time from the sub-tasks as well?

6) How to correctly show and get the workload for each employee who conducts their activities in Jira?

Thank you!

Best regards
Roman.

[Jack Brickey]

hi @Roman Mural ,

Let me see if I can answer some of your questions and give you some guidance. Generally speaking you should try to avoid multiple questions in a single post. There are many reasons for this but primarily it is so that each question Will get the proper attention resulting in improved results for you and future searchers. 

1. I would recommend creating an automation rule that sums up the original estimate into the epic each time any of the child task or sub-tasks are updated. I would like to recommend that you use the search bar here in the community to find good examples of this as there are quite a few. This is a common question that many members have.
2. There really isn't a good out of the box solution for this if you are trying to show the sum of original estimates. There are marketplace Apps that you might look into. Of course if you are using a scrum board and story points then you can look at those details by a sign when doing your sprint planning as well as when tracking the sprint using burn down charts.
3. I generally use scrum boards for this purpose. We have Sprint planning sessions where we use historic velocity to understand how mini story points the team can accomplish in a given sprint. During the sprint we monitor our progress in the daily standup meetings.
4. I don't distinguish between small tasks and large tasks other than by story points. If you are not using story points and relying solely on Time estimation then I would simply use hours instead of days for example.
5. If you are using sub-tasks then you should leave your task unestimated and do all of your estimations in the sub tasks. In other words if you're going to use sub tasks make sure it represents all of the work that needs to be done in a task and not do some of the work in the task itself.
6. This seems to be a duplicate question with 2 and 3. Ultimately depending on your requirements you may wish to have an add-on application for time management.

I hope that some of the information above is helpful.