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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I'd like to better understand the design thinking that Atlassian has put into how certain date fields are used in the two different roadmap UIs:
For me, I'd really like to have Teams use one start and one end to drive their data against a due date (as seen in the first example above). However, if the interface they are presented with most readily is the Board Roadmap, then they'd need to enter Start Date AND Target Start to satisfy both UIs.
Alternatively, does it just make sense to turn off the Board Roadmap feature entirely and have all levels of the organization use Jira Advanced Roadmaps? I've done this in the past; I was just hoping to leverage the new, simpler view...