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
Next: Root
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 used a label to pull various epics/stories from 3 scrum projects and 1 kanban project to pull into a roadmap. I can't seem to get the timeline bars to show for any of my scrum projects. At one point, I was able to get my kaban project to show a timeline bar. The scrum projects are higher priority over the kanban project, so I removed the kanban project thinking that was possibly the issue and it hasn't helped. I've tried changing the configuration settings to alter the estimation/dates and inferred dates are pulled and can't resolve the issue.
So for the Scrum project which fields are they using for start and end date data? In other words, do the issues pulled actually content a consistent dataset for generating the timeline.
I only ask as it is a reoccurring theme where I am.
Ah I see. we only use start/end dates for the Kanban project. The scrum project we only assign the stories/epics to sprints and don't have start/end dates. I assumed the timeline bars within the respective sprints would show on the roadmap view.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To get the teams timeline (and sprint) data to show on a plan, follow this View and edit teams in your Advanced Roadmaps plan | Jira Software Cloud | Atlassian Support and ensure that the inferred dates section of the plans schedule is set to "Sprint dates"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you have Shared teams set-up with their Board/s as the issue source as per the link I posted? As I think that is required for the magic to happen.
Beyond that, I'd raise it with Atlassian support.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.