Dave Atlassian Team

Hi @Alan Abosowitsch , Thanks for sharing this use case. The primary use case for Advanced Roadmaps is expected to be agile planning (e.g. scrum / kanban) and typically the issues would only be planned at most to the day, and most commonly to the sprint. We haven't had many calls for more precision on the start / end…

Hi @Luis Cano , I'm on the Advanced Roadmaps team, as @Mikael Sandberg mentioned there are quite a few videos in the "Articles" space of this section of the community: https://community.atlassian.com/t5/Advanced-Roadmaps-articles/bg-p/portfolio-for-jira-articles It would be really useful if you could give us a brief…

To add a little to what @Nic Brough -Adaptavist- said with respect to Advanced Roadmaps. We have used an approach where we create additional hierarchy levels above epic and then associate those with issue types only available in a project designed to cross-cut multiple other projects (these might be what you'd consider…

Hey @Mykenna Cepek , Would love to understand further the concerns about Advanced Roadmaps progress column to see if there's some improvements that can be made here. Are there specific use-cases where this doesn't work or do you feel like it's not accurately reflecting progress at all for some reason? It's definitely fair…

Hi @Tobias Rettensteiner , Up until recently it was available as a market place application for Server and Data Center but things have been changed recently so that it is now included with Data Center and is no longer available as a separate application for Server unfortunately. Regards, Dave

Thanks for that detailed explanation @Doug Levitt - much appreciated! It sounds like you're using a Release / Version to represent something similar to a Program Increment? This is one of those situations where probably having a hierarchy of iterations in Jira would be incredibly useful. It sounds like you can have…

Hi @Tobias Rettensteiner , Have you considered Advanced Roadmaps at all? It's now part of Data Center (for on premise) and included with Jira Premium (on Cloud) - see https://www.atlassian.com/software/jira/guides/roadmaps/advanced-roadmaps. Although we don't really consider it to be Gantt per se, it does offer what people…

Hi @Doug Levitt , I'm on the Advanced Roadmaps team and I'd to understand your use case for this feature further. Something that I've been keen for us to add to Advanced Roadmaps is to have an additional bar on the timeline to show when issues transitioned into and out of an "In Progress" workflow states (the idea being…

Hi @Tracy Moffat , To answer the last question first... we removed some of the capabilities from the tool when we developed the new interface (originally as Portfolio 3.0 on Server) because we were finding that the complexity of the tool as causing confusing. Whilst the features were powerful and some customers were…

It's worth bearing in mind the history of the auto-schedule function and it's origins from the "Calculate" scheduling algorithm in the previous interface (known as "Live Plans"). So for Live Plans the scheduling algorithm took a lot more factors into consideration and was a lot more complex to configure, see this…

Unfortunately I don't that there's a simple JQL solution for this @Exalya .... the only thing I can think is that you could create an additional hierarchy level above Initiative and then make it a parent of all the Initiatives in Project A and then use the portfolioChildIssuesOf for that issue. That's definitely a…

Thanks for sharing this information @Lopes, Bonnie Q , I'm sorry to hear that you've not been able to take advantage of the Advanced Roadmaps team field. Is the problem specifically within the Jira issue screens where the field will display all shared fields? Within a plan I believe that only teams imported into or scoped…

Thanks for sharing this information @Jean-Pierre Froud - it's incredibly helpful. It's interesting that you've gone for a team per plan approach... does that mean that individuals only contribute to one team? I'm also interested in if multiple teams work on the same Project? One of the reasons you might want to share a…

Hi @Thorsten Kamann , I've investigated this and it seems that unfortunately there's nothing we can do to assist at this point (i.e. we're can't provide a server based license for the Advanced Roadmaps application). I'm really sorry, but I thought it better to provide a direct answer than just leave this as an open…

Hi @Adidas AG , I agree with @Michael Andolfatto here... what you're describing suggests that only some of your teams have been shared. When you first create a team in a plan it is *only* scoped to that plan and when you assign that team to an issue it will appear in the Jira issue screen as "Plan specific team" (rather…

Hi @Praneetha Raghava , Advanced Roadmaps would be a great solution for this (see https://www.atlassian.com/software/jira/guides/roadmaps/advanced-roadmaps ) although as @Dave Rosenlund _Trundl_ rightly points out this is now only available for Data Center and Cloud (on Cloud it is included with Jira Premium) - I'm not…

Hey @Martin Bayer _MoroSystems_ s_r_o__ , You could well be right.... however, because @Exalya has mentioned that they are using Initiatives and has posted in the Advanced Roadmaps space then I had assumed that they have Advanced Roadmaps (either as an app on server, bundled with Data Center or on Cloud) but this might not…

Hi @jiranetworks_system_admin , Unfortunately that capability isn't available. Can I ask why you want to have a plan for each month/quarter rather than a single plan that you have multiple views of to help understand each time frame? I'm wondering if it's because of the number of issues that would be loaded into each plan…

Hi @Tracy Moffat , When you create a plan you can bring in multiple projects into it as issue sources. You should make sure that you've configured the relationships that you want to use to define the critical path in the global dependencies configuration (from the top navigation bar use "Plans" -> "Settings" -> "Advanced…

Hi @Exalya , You can use the "portfolioChildIssuesOf" function, for example you'd write JQL like this: issuekey in portfolioChildIssuesOf(INI-3) AND project = "Project B" Despite the name, this function actually returns all descendants of the issue provided - not just the children. This particular example just fetches the…

Hi @Robert Campbell , Sorry for the slow response to this question.... I was a little confused by this at first but I've done some investigation and I think it looks like "Original Story Points" is just an Advanced Roadmaps field that is only applicable for use in the Live Plans interface. It is described on this…

I don't play exactly, but my children like to on my phone... it's a good excuse to get them out for a walk, but I do find it a little frustrating that we have to stop all the time while I wait for them to catch pokémon ! I'll admit to having sneakily caught a few when they're not with me though! :) 

Hi @Jean-Pierre Froud , Thanks for starting this discussion. I’d be particularly keen to understand how you are using the features of Live Plans that you mentioned - ideally through the lens of the problem that you’re trying to solve. For example how are you currently using virtual users? What particular problem is that…

Hi @Jost Anklamm , Would this customer have user credentials to access the rest of the Jira instance? There's no really simple way of sharing a plan like this... if they don't have permission to access the boards then I think that this would prevent the issues from those boards being loaded into a plan (plans only contain…

Hi @AlbionPM , So I have to create a plan first to access advanced roadmaps? I guess the confusion here is that an "Advanced Roadmap" is essentially a plan... when you create a plan you will see 4 tabs ("Roadmap", "Teams", "Releases" and "Dependencies Report") and it's the "Roadmap" tab that you do the planning work in.…

I'm definitely not disagreeing with you @Steven Stroffolino ... and I probably agree that it would make sense to make the change pending until committed, I also agree that we could use the same approach as we do for required fields on commit... it's not that it's impossible to, just that it's necessarily a quick fix. But…

Hi @Michela Pucci Mossotti , I'd recommend either raising an issue with support ( https://support.atlassian.com/contact/ ) if you think it might be a bug or ask a more specific question in the community space and tag it with "Advanced Roadmaps" - there will be lots of people in the community happy to help, we just need to…

There are a few reasons why you can’t edit the status of an issue in a plan. The first is because Advanced Roadmaps plans are a “sandbox” environment we’d need to ensure that it was clear that the change wasn’t having an immediate effect (and if it did, then changing the status would be different from all other changes).…

Hi @Smiley me , Unfortunately not, apologies - I'm wondering if you've posted this question in the channel to get an answer as this is focused on Advanced Roadmaps (which is part of the Jira Premium offering). It be better to repost under the main Jira questions section and tag with "Structure" - this might get visibility…

Yes, you're right that a Shared Team can have plan-specific issues sources (i.e. that the same team can be associated with different issues sources in different plans). In fact the only data that is shared between plans is currently the name and the members and the other data (team type, iteration length, velocity) is…