Hi all,
I’m building a plan for a cross-dependent initiative in Jira and wanted to check the best way to visualize timeline risks. Here’s my setup and goal:
The Initiative has a defined planned start and end date.
All child issues (Epics/Stories) under it roll up their dates automatically from their sprints.
Now, let’s say an issue in Sprint A (Project B) gets moved to Sprint B, which is dependent on another issue in a different project — the dependency line turns red (as expected).
What I’m trying to achieve is:
If any of these child issues move beyond the Initiative’s planned end date, the Initiative timeline bar itself should turn RED (indicating overall plan risk).
Has anyone implemented something like this visually?
Also, is there a way to automate a notification when this happens — like when a sprint shift causes the overall Initiative to exceed its planned end date?
Would love to hear how others are handling this scenario!
Thanks!
Hi @Sruthi Vijayakumar
In Planyway for Jira dependencies are colored red in case of the risk. Here is how it looks like:
Hi Sruthi,
Yes — while Advanced Roadmaps doesn’t currently support turning the timeline bar red, there is a built-in risk indicator.
When a child issue’s date exceeds its parent (Epic/Initiative) end date or when dependency timing conflicts occur, you’ll see a yellow warning icon (⚠️) next to the affected item. This serves as a visual signal for schedule or dependency risk within the plan.
If you’d like to go further, you can combine this with an automation rule to flag or color-code those items (e.g., set a custom field like “At Risk” and color by field in your view).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Jason U for confirming that! Yes, I’ve noticed the ⚠️ warning icon when dates go out of sync . But just to clarify — does the timeline bar itself ever change color (like turn red or yellow) when that happens? or any visual indicator on the bar like the dependency red line?
Also, I’d love to understand how you set up the automation you mentioned to flag or color-code those items. Did you use a custom “At Risk” field and manually update it when a child end date exceeds the parent’s end date? Would you mind sharing the rule setup or logic you used?
Thanks again
— Sruthi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
By default, Roadmaps doesn’t dynamically recolor timeline bars (like red/yellow/green based on conditions), but you can simulate this using a supported custom field and the Color by field option.
Created a Single Select field called “Risk Status” with values like:
• Normal
• At Risk
Plan view → View settings → Colors → Field → Risk Status,
I mapped:
• At Risk → 🔴 red
• Normal → 🟩 green
This way, even though the bars don’t change color natively, they appear red when “At Risk” is selected — which gives the same effect visually.
Here’s how it looks after applying this setup 👇
This approach works perfectly because the Color by field feature only supports certain field types — like Single Select, Status, or Priority — not text or checkbox fields.
So as long as “Risk Status” is a Single Select field, you’ll see the colors just like this.
You can make Jira automatically change this field when issues are overdue:
Rule Setup:
Trigger: Scheduled → every day
JQL:
statusCategory != Done AND due <= now()
Action: Edit issue → set “Risk Status” = At Risk
(Optional) Add a second condition to reset it:
statusCategory != Done AND (due > now() OR due is EMPTY)
→ Edit issue → set “Risk Status” = Normal
This keeps the color always up to date automatically.
With Jira Automation, you can expand this logic however you want — for example:
when a sprint slips,
when a dependency issue is delayed,
or when a high-priority task is blocked.
Just define your rule logic, and Jira will handle the rest — keeping your timeline colors in sync without any manual updates.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.