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
Jira advanced roadmaps defaults to start date and due date, but we use a custom field to track the end date for issues. No matter how much education I do, teams won't always remember to update this when they first create their roadmaps - they simply dive right in.
Any help would be appreciated.
You should be able to define the start date/end date fields in your plan via plan's configuration in the scheduling option. Due Date field is a field/column that you can expose/hide to your plan as needed. If you set the Due Date value in your issues within your plan, you will need to commit the changes back to Jira (otherwise, it is local to your plan only).
Hope this helps.
Best, Joseph Chung Yin
Jira Functional Lead, Global Infrastructure Apps
Thanks! I'm aware of how to add the custom fields and update the date fields under the plan settings, but my challenge is that teams often forget to do this. They build a plan and start adding start and due dates when they should be using a custom end date.
Any way to adjust the default dates that the plan uses upon creation?
Currently, we didn't find anything to default the values. I would recommend that you submit an enhancement request with Atlassian.