nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automatically propagating task dates to stories and epics in Jira for timeline visibility

Peter Tikhomirov_revgz4

Hi everyone,

I’m working on setting up a new structure in jira. I'm thinking about tasks are linked to stories using the parent field, with the goal of providing start and due dates to the stories and then passing them up to the epics. Ideally, I want the system to automatically gather the earliest and latest dates from tasks, update the stories, and then the epics, so that I can see on the timeline when each epic will start and be completed.

Is this possible with the current Jira Premium setup, and if so, how can I configure it?

Or maybe there are other options and I just don't see it

Accepted answers

All comments

Marc -Devoteam-

HI @Peter Tikhomirov

Your setup can't be achieved.

Story and Task are o the same level in the hierarchy in Jira, you can't use the parent field for this.

Task and Stories can be linked to Epics via the parent field.

Trudy P Claspill

Hello @Peter Tikhomirov

Welcome to the Atlassian community.

Do you want the dates actually recorded in the issues? Or would it be enough to see the times rolled up without recording them at the parent levels?

In the Premium subscription you have access to the Plans feature (fka Advanced Roadmaps). In the Plans feature you can set your Timeline View Settings to show rolled up dates.

Screenshot 2024-10-15 at 1.18.59 PM.png

This doesn't actually record the dates in higher level issues. It only display the information in the Plan Timeline view.

If you want to actually record the dates you could do that through Automation Rules.

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

You would need to decide what type of issue event would cause the update to occur, as that determines the rule Trigger you would use.

Peter Tikhomirov_revgz4

I think the roll-up will work fine. Is there a way to link tasks to stories without using linked issues? Or does this approach mean that all task dates with the “is blocked by” link type will be rolled up into the stories?

Marc -Devoteam-

HI @Peter Tikhomirov

No you need to use linked issues option to link issues together.

You can use other link types as well, but then you will need to access the Plans 'global' settings and in the Dependencies setting, add the issue link types you want to also use in a plan.

Peter Tikhomirov_revgz4

But Premium mentions that I can change hierarchy. Isn't it true?

Marc -Devoteam-

Hi @Peter Tikhomirov

Yes based on new created issue type, but no on the default in system issue types.

That hierarchy is always Epic, Story level (includes Story, Task, Bug), Sub task level

Peter Tikhomirov_revgz4

Sounds great! Thanks a lot!

Trudy P Claspill

@Peter Tikhomirov

The native issue type hierarchy is

Level 1 - Epic issue type
|-- Level 0 - "standard" issue types; i.e. Story, Task, Bug
    |-- Level -1 - subtask issue types.

Jira does not support inserting another level in this base hierarchy.

The Premium subscription allows you to add levels above Epics.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-work-management

jira-work-management-cloud