Dave Atlassian Team

Hi @Peter Yoon, It's configurable in the plan settings - but by default on Cloud it uses the Start Date and Due Date fields (on Server the defaults are Target Start and Target End). You can surface all these fields on issue details screens so that they can be viewed / edited directly on an issue. Regards, Dave

It looks like you haven't assigned any of the issues to any teams. You'll need to make sure that you've created teams (from the "Teams" tab) and then associate each team with a board that sprints. It's worth noting that you need to use boards as issues sources for your plan (as this is where sprints come from). You then…

Hi @Peter Yoon, Capacity planning for Advanced Roadmaps is also available on Cloud, you access it by using the view settings menu to group by either Team or Sprint and then there is a checkbox "Show capacity on the timeline" that you can enable. However - I notice that your question is tagged to indicate that you're on the…

Hi @krista.phillips, This is a known issue caused by a change in the checkbox component that we're using. However the fix is unfortunately blocked behind from deployment by other changes. At the moment I'm unable to give a timeline of when the fix will be deployed. Regards, Dave 

No worries, @Yen Pham - glad I was able to help!

Thanks for sharing this requirement @Rebecca C. Unfortunately we don't have any plans to implement anything like this in the near future for Advanced Roadmaps. It might be possible that another marketplace application has something that can assist in this regard though. I appreciate that this isn't a great answer, but I…

Hi @Dina M, The older user interface for Advanced Roadmaps (known as Live Plans) had the concept of a themes that you could apply across multiple hierarchies of issues however we didn't include this in the new feature because the data was only accessible within a plan and it wasn't visible within the rest of Jira. It…

Hey @Mike Lemmon, It could be that you're on an older version of Jira and don't have this feature yet (what version are you currently using?). If you're not seeing the ability to set the start and end dates when editing future sprints from a backlog then you don't have this feature. In which case I'm really not sure what…

Thanks for the clarification ... unfortunately it's not currently possible to show the time logged in this way (within Advanced Roadmaps), however the approach I described should at least allow a projected estimate to be shown as well as giving an overview of progress. Regards, Dave

Hi @Yen Pham, Is the greyed out issue a descendant or an ancestor of an issue that matches the filter? For example, if your hierarchy range is set from Initiative to Story and you have an Epic matching the filter then the ancestor would be the Initiative and the Story the descendant. You can prevent descendants from…

Hi @Mike Lemmon, This will be dependant upon the version of Server (not Advanced Roadmaps) that you're using... the ability to configure future dates was added a while ago now though IIRC. The way to tell is to edit a future sprint from the backlog page and see if you have the option to set start and end dates for that…

Hi @Karyl Crick, Some additional context might be useful here... are you on Server / DC or Cloud... and if you're on Cloud are you using a Team Managed or Company Managed project? I believe that the UX is subtlety different in some cases as to how you add the epics panel. Regards, Dave

No worries @Gonchik Tsymzhitov ... My team meets on Zoom every day at 11am. I usually get a general line of conversation going as everyone joins then after a few minutes once everyone has joined I'll kick off the updates usually starting with person that joined first, they then nominate the next person. Once all updates…

Thanks for confirming the version @David Lam, that sounds concerning - this might sound like a stupid question, but can you also confirm that the parent link is correctly set between those epics and initiatives? Also, the inherited date won't show up in the same way that the sprint inferred dates do ... it will actually…

Hi @Andries Becker, I guess the key question here is exactly what information you're hoping to report on? One of the ways that we've used Advanced Roadmaps at Atlassian is to create additional hierarchy levels above Epic (typically called Initiative - but they can be called whatever you want, and you can add as many levels…

Hi @Joe Moss, Unfortunately this isn't possible at the moment. Although it won't exactly help it might benefit you to group by Release as this might help give you an idea of where the issues in the release fall on the timeline. One piece of feedback we've received is that people would like to see values roll up to the…

I'm glad you were able to resolve this situation @Thayne Munson - did this require a reload of the plan to fix things? Or was it just a time delay with the page loaded. Regards, Dave

Hi @Sagar Mahajan, The link you've provided is for Advanced Roadmaps documentation, but @maximiliano_garces's question is tagged as "standard" not "premium" so I suspect that they might not have access to Advanced Roadmaps but are referring to Roadmaps. However, I'm not aware of any specific permissions that prevent a user…

Hi @Mike Lemmon, Although there might not be a gap between sprints, it's still possible to create a gap by specifically configuring the start and end dates for a future sprint. Previously future sprint dates would be calculated entirely based on the order they appear in the backlog and the iteration length configured for a…

Great - thanks @Kristen Roth !

Hi @David Lam, What version of Advanced Roadmaps / Portfolio are you using? The ability to roll-up dates wasn't available in all versions to you might need to upgrade to take advantage of this capability. It also needs to be enabled in the plan settings, Regards, Dave

Hi @wendt279, As @Trudy P Claspill says, Advanced Roadmaps does not yet support Team Managed (formerly known as "Next-Gen" projects), however this is something we're looking at but it's not likely to be something available in the immediate future. See here for further…

When we were all in the office our daily stand-ups were very much "all business" and very focused on the current state of play and the things everyone was looking to achieve that day (with the risks, blockers called out, etc). However since lockdown has started and our stand-ups are done over Zoom I've tried to make them…

One of the key things our team has found with DACIs is to not let them run too long. Setting a distant due date can let it linger without progress and often you only get a flurry of activity towards the end - definitely important to set a realistic due date. They're great for asynchronous collaboration on a decision but…

This is an interesting play, do you think this would work when taking on a new team or would this be something you only do with teams that you've been in for a while?

Welcome to the Atlassian Community @Allison !!

Welcome to the Atlassian Community, @Marinelle.vanDongen !! Glad to have you aboard! 

Hi @Joseph Chung Yin, you will see all the hierarchy issues without any view to display the parent child relationship. Can you explain this a bit more as I'm not sure I understand? You can the parent link field to the issue screen so you'd still have visibility of the hierarchy. I'm not familiar with the JQL functions…

Hi @Mike Lemmon, Are you on Server / DC or Cloud? On Server / DC it is possible to configure future start and end dates on future sprints (this isn't available on Cloud yet but is coming soon). That would be one reason for the gap appearing. Regards, Dave

Hi @Joseph Chung Yin, Yes - that's a fair point. The main disadvantage here is that you're not going to have Epics in the backlog sidebar on a board (I'm not sure what other functionality you'll lose?) but given that all the other hierarchy levels will also appear in your backlog it might be more consistent to have…