1. Project includes stages
2. Stages include tasks (they have different default estimates)
3. Each stage starts when the previous stage has been completed only (means all entire tasks are completed)
4. If any task goes over due - stage misses deadline and shifts all roadmap for this delay time
5. Save the template of this project with stages and tasks
2. Stages (maybe Epics)
Stage includes tasks and has deadlineTask has estimate
It means thatStage Printing is time bounded: jul.14.2019 - jul.24.2019 (10 days)
Task 1 is load paper 1 day
Task 2 is print 3 days
Task 3 is get prints 2 days
Task 4 is delivery 5 days
if Task 3 takes more than 2 days (eg 5 days) - Stage Printing endtime becomes jul.27.2019
Welcome to Atlassian community.
Checking the description of the scenario you want to implement, I understand that you would like to configure Epics (Stages) with the total amount of the linked tasks work estimation, so when you update the estimation of any of the tasks it should count in the Epic estimation too. Have I understood it correctly?
If that's the scenario you would like to achieve, you just would need the free third-party add-on Epic Sum-up Light to automatically sum task estimations to their respective Epics.
That been said, I also would like to suggest a different approach:
The estimation fields are used to calculate the estimation of the tasks, so you can have how much work you actually logged vs how much time you estimated for it.
With that establishment in mind, instead of using Epics and reorganizing estimation values when the work logged trespasses the original estimation, I think you could use Sprints as the Stages to properly track your issues.
Using Sprint as stages, you will have a real start and complete date (This one is set when you finish all the tasks and close the Sprint) and you'll use the estimation field to check how much time you have initially planned for it.
Additionally, you will have several Reports that you can use to check which tasks have fallen behind the clock, together with many other functionalities you want. Check the section "Reports for Scrum Projects" in this documentation for more details.
If you get interested in this approach, please check the documentation below to know more about the Sprint functionality in Scrum boards:
let me know if you have any other questions.
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events