You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
I'll answer my own question after 16 months of usage.
Best to use Start Date and Due Date. No need for Target/Planned Start and Target/Planned End as any Start Date/Due Date in the future is "target" and any Start Date/Du Date in the past is "actual".
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.
A Target/Planned Start Date is needed for the Gantt chart, which some people love for sharing as a visualization with Business partners.
Some teams enjoy using the Target/Planned Start Date for managing the backlog - thinking of starting on time helps finish on time, and also helps sort through the clutter of things that don't need to be started until, say, next month.