You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
So, after several months, we opted for Jira Premium. I created a plan and noticed all these warning signs. They are all related to dates
I added 'Dates' tab with custom date fields to all issues in Jira, including epics and subtasks
Using these fields I can filter issues in the issue navigator which I found useful.
The thing is, I do not know how dates should be managed in Jira. What are the best practices?
Currently, I have a standard hierarchy level (Epic -> Story/Task -> SubTask), but it will be adjusted. The new one will be Theme -> Initiative -> Epic -> Story -> Subtask.
My question is, how should dates be managed? Should parent issues inherit dates from child issues, or vice versa? Or what should I do? Should I somehow automate date fields?
In addition, I now have the Roll-up functionality in 'View Settings.' From what I understand, this functionality is directly linked to dates as well. In my case, it does not show up on the timeline because, as you already know, I don't have a proper protocol for dates. Maybe someone could elaborate how to use this functionality peoperly.
There is no official guideline on how to use dates on a hierarchy level of tickets. But there are some best practices in a couple frameworks, such as Scrum.
Let's say you have the below example following your hierarchy scheme: Theme -> Initiative -> Epic -> Story -> Subtask
----- Subtask (due 12/20)
Considering that they are hierarchically related, since the last subtask is due on 12/20, this date should be replicated to the above types. By definition, a story can be marked as resolved only when all subtasks are completed, and that follows the same logic for Epics and Initiatives.
I would strongly recommend using Jira default date fields, such as Start Date and Due Date.
Hope this can help you define your date structure.