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; } } }

Trying to use Adv Roadmaps to build a template for several tasks facilitate a release.

gordon.varney

Ideally, I build this template, including mapping the dependancies and nominal time expected to complete each task. Some a re serial tasks, some are able to be done in parallel.

Within the structure of the template, with dependancies set and nominal time for each, I'm hoping that by setting the last day for the4 last task, everything will adjust backwards showing me when things Ideally should be started. With that insight, I can map the release tasks into our existing sprint cadence.

Is doing this (or even getting close to it) possible? Is the a different/better/easier way to do it?

Cheers.

JGV

Accepted answers

Trudy P Claspill

Hello @gordon.varney

There is not a native, single-button-click solution for that.

I wrote an article about automatically adjusting dates for successor task when the date on a predecessor task changes. What you want to do sounds a bit like the reverse. You might be able to extrapolate a solution from what I wrote.

Updating dependent task's dates when predecessor task date changes

All comments

Trudy P Claspill

Hello @gordon.varney

There is not a native, single-button-click solution for that.

Updating dependent task's dates when predecessor task date changes

gordon.varney

Interesting, nice bit of code.

I'm doing this up in Advanced roadmaps though, so unless I'm mistaken, can't write this automation in that enviro.

Maybe I can move it all down in to Timelines....hmmmm.

gordon.varney

Nope, can get to sub-tasks in Timeline...

I guess I could move everything up one level - don't want to though.

Trudy P Claspill

Hello @gordon.varney

Can you elaborate more on what you mean by "doing this up in Advanced roadmaps"?

It is true that there is not an Automation Rules feature embedded within Plans, but changes made to Plan-referenced issues by Automation Rules should be reflected in the Plans.

Plans typically reference issues from projects/boards/filters. You can make speculative changes in the Plans view without committing those changes back to the underlying issues/projects. Are you creating issues within Plans and/or making changes to existing issues within Plans, but not committing those changes?

Your Plan can reference the live data currently associated with the Jira issues. So if you ran an automation to update dates in those issues, it should be reflected in your Plan. You may have to refresh your Plan to see the changes made by the automation.

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-cloud

advanced-roadmaps

dependency

original-estimate