Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Epic roadmap: how to place epics in roadmap based on sprints planning

Hi all, 

I'd like to know if there's a way to automatically see epics in the roadmap based on the epic sprint and on the tickets sprint belonging to a specific epic. 

For instance:

- I have an epic called "Epic 1" with 25 stories 

- I put all the 25 stories in the Sprint 35, that goes from the 1st of June to the 30th of June

- I'd like to see the Epic 1 placed in the roadmap under the Sprint 35 and the month of June 

I attach a screenshot: 

Screenshot (2).png

Right now I have all tickets belonging to the epic Cart planned in the sprint 35, but the bar is not showing up in the roadmap. 

I've also tried to give a sprint to the epic, but still no results. 

Thanks in advance for the help!

1 answer

Hi @Virginia Morrone  -- Welcome to the Atlassian Community!

The epics on the Basic Roadmap display based on the Start Date and Due Date fields.  You would need to set those fields to have the bars display.  Often an epic is a large body of work and so could span multiple sprints, so please consider that if it fits your case.

You could set the epic's date fields manually, use a scripting addon, or use an automation rule based upon changes to the sprint field (or the child issues).

Assuming your epics fit in one sprint, you could use this automation rule if you set the sprint manually:

  • Trigger: sprint field changes
  • Condition: issueType is epic
  • Action: edit issue fields, changing the Start Date to the sprint starting date and Due Date to the sprint ending date

With a more complex rule, you could let the child issues drive the parent's date range.

To learn more about automation, please look at these examples and documentation:

Best regards,


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

322 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you