Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Managing dates in Jira Premium

BenWade
Contributor
November 8, 2023 edited

Hi everyone,

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


image.png

image.png

image.png

 

I added 'Dates' tab with custom date fields to all issues in Jira, including epics and subtasks
image.png

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.
image.png

1 answer

1 accepted

2 votes
Answer accepted
eugenio_onofre
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 8, 2023

Hi @BenWade

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

- Theme
-- Initiative
--- Epic
---- Story
----- 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.

Best Regards!

BenWade
Contributor
November 8, 2023

Thank you for your help, Eugenio. This absolutely sounds logical. 

Waht about roll-up functionality. What dates does it follow?

Suggest an answer

Log in or Sign up to answer