Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Best practice for start/end dates in Advanced Roadmaps

I'm starting to roll out Advanced Roadmaps in our organisation. It's a relatively mature Jira instance so it has a number of custom fields for start/end dates depending on the context.

Are there any best practices for selecting which date fields should be used for start date / end date in Advanced Roadmaps? When I create a brand new plan it defaults to "Start Date" (custom field 12010) and "Due Date" (the in-built field).

How do others have this set up?

Are people tracking planned dates and actual dates separately? I'm thinking that's not very relevant when planning using scaled agile techniques.

2 answers

We're a mature instance but just getting started with Advanced Roadmaps.  We are using Planned Start (custom) and Due Date.

0 votes
elizabeth_jones Community Leader May 25, 2021

I have custom fields for Target Start, Target End, which is what drives my roadmap gantt chart. I also use start, due date for tracking actuals to plan. 

Hey @elizabeth_jones 

can you share a bit more on your setup? We are trying to do the same but it seems Warnings are not working on such setup. We want to see a warn when Start date is later than Target start date.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events