Dave Atlassian Team

@Savitha Gurumoorthy , @Joseph Chung Yin - thanks for sharing those screenshots. I think that those appear to be bugs so I'm confused as to why I can't reproduce that problem. I would recommend that you both contact your support representatives to investigate this issue. It's not something that we can really dig into in…

Hi @Thayne Munson , We would actually like to provide support for multi-line text fields in the future but this is not on our short term roadmap at the moment. One of the challenges we have is in finding a design pattern that works well to support multi-line data (see also the main description). Our current design is to…

@Savitha Gurumoorthy , @Joseph Chung Yin - I've been experimenting with this on both my Server and Cloud platforms and I've not been able to reproduce what you're describing. In both cases I'm seeing different colours assigned for each project. Is there some subtlety in the problem that I'm missing? Perhaps you can include…

Hi @Ramin Raiszadeh Whilst it's not possible to have different hierarchies within the same instance, it is possible to have different issue types that different projects use at that level. So for example, let's say that I add a level called "Initiative" above "Epic". I can create two different issue types called…

Hi @JD , I just checked this to be sure and unfortunately it doesn't (although I can see why you would think that it should). It just updates the "Remaining estimate" field when setting an estimate for the first time. Regards, Dave

Hi @Bharat Bhatia , I would probably recommend reaching out to support for something like this rather than raising a community request. This doesn't look correct to me, but I'm not sure it will be possible to provide an answer via the community channel, Regards, Dave

Hi @Itay Smira , Rather than trying to write my own summary of the process, I'd recommend that you review this documentation page https://confluence.atlassian.com/advancedroadmapscloud/configuring-hierarchy-levels-998650959.html as it takes you through the whole process in some detail, Please let me know if anything in…

Hi @[deleted] , It is possible, but I completely agree that this can be a challenge. As you'll see in this screenshot if you start constructing a JQL query you will get "Team" as an option (and in this case we actually have multiple team fields so you have to choose the right one, and this unfortunately is not always…

Hi @James Cast , Could you provide some more information on how you've set up your plan? When you create a plan you need to provide one or more issues sources which can be either projects, boards or JQL filters. If an issue appears on an issue source (e.g. you see it the JQL filter results) then in general it will appear…

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

Hi @jd I just want to make sure I understand correctly ... when you say: the "Estimate" field is being populated by the team ...is this in the Advanced Roadmaps plan interface or in the main issue details view? If this is in the plan (e.g. under the "Estimate (h)" column) then when you save that change back to Jira it…

No worries @Joseph Chung Yin - we really appreciate all the answers you provide to the community - and I understand that this is not necessarily an easily discoverable feature!

Hi @JD , The estimate field is mapped to the "remaining" estimate rather than the original estimate field in order that time tracking can be used. It would be useful to know what you're trying to do ... are you trying to change the original estimate after it's been set at the end of a sprint for example? Regards, Dave

Hi @Shob , If you have 2 issues (lets call them "A" and "B") and you've created a dependency relationship between them so that "A" blocks "B" then the auto-schedule function will take that dependency relationship into consideration. However, there are 2 modes that you can configure in a plan for dependency scheduling. The…

Hi @[deleted] , I just wanted to confirm whether you just want to recreate the hierarchy in Advanced Roadmaps or if you want to synchronise with an existing hierarchy that already exists in Structure. If you're looking to simply recreate the hierarchy then it is possible to add additional hierarchy levels for plans -…

Hi @Satyajit Baral With Advanced Roadmaps (which is a part of Jira Premium) you get the ability to add additional hierarchy levels above epic so it would be possible to have a higher level issue type with multiple Epics linked as children. This is only available with Advanced Roadmaps though so you would either need Jira…

Removing my previous answer because I now realise it was actually incorrect - apologies for any confusion. Regards, Dave

Removing my previous answer because it was incorrect - apologies for any confusion caused. Regards, Dave

@Joseph Chung Yin thanks for providing an answer but unfortunately you're incorrect in this instance as bulk rank is available in plans (please see the answer I've provided) Regards, Dave

@Susan Stoba yes, it is possible to bulk rank in Advanced Roadmaps. This is available in both the Cloud and Server versions. Select the issues you wish to rank and the use the "Bulk actions" menu that is shown when issues are selected. In this menu there is a "Rank" option and you can rank to the top or bottom of the plan…

Thanks for the update @NAYANA this should at least give us the right environment to try and reproduce the problem on. This does seem to be unexpected behaviour as I don't believe that issues in an active sprint should be changed and it might be that we've fixed this on a release after 3.24.0 - we did make a number of…

Hi, In order to help understand what is happening it would be really useful to get some more information. First of all are you using Cloud or Server? If you're using Server, which version are you using? Can you also confirm whether or not you have configured the plan to schedule dependant issues sequentially or…

The main reason for this is that Advanced Roadmaps is considered to be a forward planning tool. When a plan is loaded it only fetches issues that have been resolved recently (the number of days can be configured for each plan, but defaults to 30). This is done in part to reduce the number issues that are loaded because…

I just wanted to make a minor correction to the answer. Hierarchy levels were not introduced to replace themes - the previous interface for Advanced Roadmaps (known as "Live Plans") already let you add additional hierarchy levels. I've provided a more detail explanation…

Hi Stuart, The concept of Themes still exists in the older "Live Plans" interface of Advanced Roadmaps, but is not present in the new interface. To understand the reasons for this it's worth digging a little into the history. Advanced Roadmaps was previously known as Portfolio for Jira. The new Advanced Roadmaps interface…

Hi Chris, For the server version of Advanced Roadmaps (formerly Portfolio) we added a dedicated issue search feature that allowed you to find issues in a plan, see this server documentation for more details: https://confluence.atlassian.com/advancedroadmapsserver/searching-for-issues-998867215.html We will be brining this…

@Alex GON Not at the present time. Roadmaps are available for Cloud which include exporting to Confluence pages: https://confluence.atlassian.com/jirasoftwarecloud/roadmap-957979308.html

@Alex GON Do you mean Confluence Cloud users (i.e. sharing plans from Jira Server into Confluence Cloud)? Or Portfolio Cloud users?

Hi @Matt Marcus , Can you confirm which version of Portfolio that you're using please? Judging from your description it looks like you're not actually assigning the issue to a sprint. When you group by team and choose to view capacity on the timeline you will see the sprints (if there is a board associated with the…

If the due date is earlier than the target date than that definitely should show a warning. The due date should be considered as the date the issue absolutely must be resolved by. You can have a target date that indicates the issue will be resolved before the due date, but if you're targeting to resolve an issue after it's…