youngmon/atlassian-qna huggingface dataset:
How do I get "team sprints" to link directly to Teams?
Asked by Leopold van Lynden:

![Screenshot 2020-11-20 at 11.19.19.png](/t5/image/serverpage/image-id/119115i2308E9F6769C5A5B/image-size/large?v=v2&px=999 "Screenshot 2020-11-20 at 11.19.19.png")Above you can see how my sprint scrum board pulls through to the teams view planner in AR. I'm not sure if we're set up wrong in JIRA or AR but basically in JIRA we hvae four simultaneous sprints for each fortnight.

We know the capacity for each team and we schedule the work into each sprint. I've then created Shared Teams in AR, assigned users and capacity and put the issue source to the Sprint Planner scrum board, which all kind of works but leads to this weird view of having multiple sprints per team - definitely not doing something right here.

Should we just have one sprint per period and differentiate the teams differently? We currently use labels to mark which tasks are for which team so we can filter the capacity in the backlog sprint view. This is has been driving me insane for about a month now! Any suggestions would be greatly appreciated! Thank you.


Answers:
author: Dave
body: Hi [@Leopold van Lynden](/t5/user/viewprofilepage/user-id/4143448) ,

I suspect the reason that this is happening is that you only have one board as an issue source for the plan and that all the sprints appear on that board?

The way that I would recommend you set up your plans / boards would be as follows:

1. Create your plan
2. Create teams in the plan for each team and use Share them so that they are visible from issue details pages
3. Create a JQL filter for each team (e.g. projects = "PRO" and team = "Team 1")
4. Create boards in the project from each of the filters that you've created
5. Go back to the plan and add in each of those boards as additional issue sources
6. Go to the "Teams" tab and then associate each team with the appropriate board (via the "Associated issue source" menu)

That way you'll only see the sprints from each teams board. This also means that each team gets their own board (which can help with planning).

Hopefully that all makes sense and I've explained it clearly, but if not please let me know and I'll provide some more details

Regards,

Dave

comments: author: Leopold van Lynden
body: Thank you very much Dave, really appreciate the feedback. Going to try this out and will report back. Thank you!


author: Leopold van Lynden
body: Hi [@Dave](/t5/user/viewprofilepage/user-id/1183605) that worked so think we're all good, thanks for helping, massive appreciation. :)


author: Dave
body: No worries [@Leopold van Lynden](/t5/user/viewprofilepage/user-id/4143448) - glad I was able to help!


Tags: advanced-roadmaps
Adding 'Priority' field to Filters
Asked by Daniel Barber:

I have set up an advanced roadmap under Plans that feeds off of a dozen or so Jira projects. I want to be able to only show issues with a certain priority level, e.g. Blocker or Critical. I can see the option to show it under Fields but that does not allow me to only show one or two priority types. Is there a way to make it a selectable option under Filters so that I can limit the view to only specified priority types?


Answers:
author: Joseph Chung Yin
body: [@Daniel Barber](/t5/user/viewprofilepage/user-id/3784126) - It looks like currently there is no option to use Priority as a filter in AR plan. I found this enhancement request -<https://jira.atlassian.com/browse/JPOSERVER-2643> for this ask.

Given the above finding in AR, you can use custom fields to use as filters. But this means that you will need to create the field in Jira and tag your issues in your projects using the custom field(s). Afterward, you should be able to create your filter in the plan.

Here is the link on Filtering issues in AR - <https://confluence.atlassian.com/jiraportfolioserver/filtering-issues-962968235.html>

Hope this helps.

Best, Joseph Chung Yin

Jira/JSD Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

comments: author: Daniel Barber
body: Thank you for your quick reply


Tags: advanced-roadmaps

cloud
Export/Sharing of advanced roadmap
Asked by intan:

if a share a read-only view, will our stakeholders (without atlassian credential) be able to see our advanced roadmap?


Answers:
author: Walter Buggenhout
body: Hi [@intan](/t5/user/viewprofilepage/user-id/4166722),

The documentation is not outspokenly clear on the topic. [In the server version](https://confluence.atlassian.com/advancedroadmapsserver/sharing-and-exporting-plan-data-960719459.html), there is an explicit mention that your stakeholders need *view plan permissions* in order to see the shared roadmap.

The below statement from the [cloud documentation](https://confluence.atlassian.com/advancedroadmapsserver/sharing-and-exporting-plan-data-960719459.html) at least suggests that this permission is not necessary:

![Screenshot 2020-11-22 at 09.26.14.png](https://community.atlassian.com/t5/image/serverpage/image-id/119233i8628CE1BE6C2D4C4/image-dimensions/556x102?v=v2 "Screenshot 2020-11-22 at 09.26.14.png")

You didn't mention your hosting type in your question, but assuming you're on cloud, give it a try!
How can I adjust the weekly capacity for individual team members
Asked by Jonas Kwaschik:

Since I want to utilise advanced roadmaps for ressource planning and forecasting I need to set individual capacity for each team member, as not everyone has a standard 40 hours work week. How and where can I do that?


Answers:
author: Ravi Sagar _Sparxsys_
body: Hi [@Jonas Kwaschik](/t5/user/viewprofilepage/user-id/4167350)

Take a look at this page where you can check the [limitations](https://confluence.atlassian.com/jiraportfolioserver/future-releases-and-limitations-953663163.html) of the improved interface. Basically you have manage that at the team level.

Ravi

comments: author: Jonas Kwaschik
body: Thanks Ravi, so I would basically setup a new team for each team member.


Tags: advanced-roadmaps

cloud
How do you cascade Team to each and every Initiative, Epic and Story without doing it one by one?
Asked by Pierre Legrand _Contractor_:

In Portfolio you used to be able to cascade the team name from Initiative to Epic to Story by just assigning the team to the initiative or Epic. How do you do it in Advanced Roadmaps?


Answers:
author: Walter Buggenhout
body: Hi [@Pierre Legrand _Contractor_](/t5/user/viewprofilepage/user-id/4133725),

You could use bulk update for this. Select the items you want to update simultaneously using the check boxes in front of them. Then, through **bulk actions** update the team for the whole set:

![Screenshot 2020-11-20 at 16.06.22.png](https://community.atlassian.com/t5/image/serverpage/image-id/119130i56ACDCA132E33F4D/image-dimensions/270x357?v=v2 "Screenshot 2020-11-20 at 16.06.22.png")

The automatic cascade in the old Portfolio was definitely quicker than this, but it is a workaround that is still a lot quicker than doing it one by one.

To help you make the selections quicker, it is an option to use filtering combined with the select all checkbox at the top of the scope table. In the example of my screenshot, I went about as follows:

1. Set the hierarchy to span the levels from Portfolio down to Sub-Task (so all issues in the hierarchy are visible)
2. Applied a filter to select just 1 initiative (based on issue key) and made sure to display the full hierarchy
3. Clicked the select all checkbox at the top of the list
4. Deselected the Portfolio issue that I didn't want to update (I could have excluded that by limiting the hierarchy in step 1 as well)
5. Start the bulk action

comments: author: Pierre Legrand _Contractor_
body: Doh!!! Hiding in plain sight! Many thanks for this. Wish that it was automatic if there was just one team.


Tags: advanced-roadmaps

cloud
Create Hierarchy Levels
Asked by Wansze Kong:

We are attempting to create hierarchy levels as follows:

Initiative \> Epic \> Story \> Task \> Sub-task

I have tried linking, using the Parent Link field, and creating sub-tasks, but the visual does not seem to update on my Plan through Advanced Roadmaps.

Any assistance with this inquiry will be much appreciated.

Thank you,

Wansze Kong-Chan


Answers:
author: Walter Buggenhout
body: Hi [@Wansze Kong](/t5/user/viewprofilepage/user-id/1149481),

One thing you are trying to do is not possible: you cannot hierarchically rank tasks under stories, as they are by design in Jira at the same hierarchy level.

The default hierarchy works like this:
> Epic
>
> \>\> Story / Task / Bug *(essentially all issue types that are not Epics and not sub-tasks)*
>
> \>\>\>\> Sub-task

You can extend this with advanced roadmaps towards the higher level. So indeed, you can add an issue type **Initiative** and in hierarchy configuration add it at the level above Epics.

Once that is in place, you should see the full hierarchy available in your plan. It may look somewhat like this:

![Screenshot 2020-11-19 at 19.34.21.png](https://community.atlassian.com/t5/image/serverpage/image-id/119020iBF1512E4FACE3F86/image-dimensions/348x234?v=v2 "Screenshot 2020-11-19 at 19.34.21.png")

Even if your issues aren't linked together yet: if you see this hierarchy from the select options in your plan, you can be assured that at least your hierarchy configuration is configured correctly.

Then, it is good to know that the way issues are linked to the different levels of the hierarchy may be different depending on the level you are at. The links work like this:

* Story \> subtask: as a subtask can only be created from within a task / story, the link is based on this default relationship.
* Epic \> Story / Task: based on the Epic link of the story / task
* Initiative \> Epic *(and higher up)*: based on the parent link of the epic

Make sure that you have issues of all levels properly imported in your plan. As of then and respecting the above context, you should be able to start connecting them together. That is even possible by dragging and dropping child items onto their parent issue.

Have a look at [the documentation](https://confluence.atlassian.com/advancedroadmapsserver/planning-work-952623588.html) to find out more.


Tags: advanced-roadmaps

server
In terms of issue links, how are dependencies defined in Advanced Roadmaps?
Asked by Rob Horan:

I am trying to find a document that clearly states what the link relationships used by Portfolio/Advanced Roadmaps are, but can't find anything. Is there any place that lays out the link types, outgoing, and incoming?


Answers:
author: Irina Mosina _TechTime_
body: Hi Rob,

You should be able to configure any type of link type to be displayed as a dependency in Roadmaps (Plans) settings. You do need to have Advanced Roadmaps Admin permissions to access that. Please note that this setting is global and will be applied to all your plans.

![Plans_Dependencies.png](https://community.atlassian.com/t5/image/serverpage/image-id/118563iDC91DD5C6225FD18/image-dimensions/476x170?v=v2 "Plans_Dependencies.png")


author: Angus Russell
body: To add to Dave's answer, here's a video demo - [https://www.youtube.com/watch?v=eQu5VsUqyZA\&ab_channel=Atlassian](https://www.youtube.com/watch?v=eQu5VsUqyZA&ab_channel=Atlassian)


author: Dave
body: Hi [@Rob Horan](/t5/user/viewprofilepage/user-id/853604) ,

By default the "blocks / blocked by" relationship is used to define a dependency in Advanced Roadmaps but you can actually configure it to use any relationship type to be considered a dependency.

From the "Plans" menu select "Settings" and then "Advanced Roadmaps Dependencies" from the sidebar menu on the left. This should take you to a screen that looks like this:

![Screen Shot 2020-11-17 at 1.09.49 pm.png](https://community.atlassian.com/t5/image/serverpage/image-id/118562i904BF6486BB570DB/image-size/large?v=v2&px=999 "Screen Shot 2020-11-17 at 1.09.49 pm.png")This allows you to configure the link types that are considered dependencies. When you add a new dependency from within a plan you will be given the choice of which link type you want to use.

I hope this help!

Regards,

Dave


Tags: advanced-roadmaps

dependency

issue-link
Use custom date fields in Advanced Roadmaps
Asked by Alessa Jaeger _LSY_:

Hi to everyone,

I am trying to configure my Plans scheduling so as to use custom date fields as a basis. I am JIRA Administrator as well as Advanced Roadmaps admin, however, I have one plan where I am able to define my start date out of several possibilities:![start date dropdown.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/118436iA801259268A87EDF/image-dimensions/325x194?v=v2 "start date dropdown.PNG")

and some where it doesn't work although the custom fields are on all screens and also added as custom fields within the plan:

![Planned dates.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/118443iFF70F81C4EE67672/image-dimensions/516x121?v=v2 "Planned dates.PNG")![Unbenannt.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/118440iC3880500519B6ED3/image-dimensions/294x109?v=v2 "Unbenannt.PNG")

I'm obviously missing something, but I don't get behind it. Any ideas?

Thanks in advance,

Alessa


Answers:
author: Dave
body: Hi [@Alessa Jaeger _LSY_](/t5/user/viewprofilepage/user-id/3902055) ,

I'm going to assume that these plans are configured with different issue sources and that for the plan with more options your issue sources include projects configured to use the listed custom fields, but for the plan with fewer options the projects configured don't have any date type custom fields?

Could you investigate and let me know if that is the case. All projects included in the plan will need to have access to the same custom fields for them to be an option.

Regards,

Dave

comments: author: Alessa Jaeger _LSY_
body: Hi [@Dave](/t5/user/viewprofilepage/user-id/1183605) ,

For the plan where I don't can't set the date fields as wanted, the issue source is only one kanban board with JQL "project = XX AND (issuetype in (Epic, Story, Bug) AND Team = YY OR issueFunction in subtasksOf("project = XX AND Team = YY and issuetype in (Epic, Story, Bug)")) ORDER BY Rank ASC

I want to use the custom date fields "planned start" and "planned end". I set them to all screens within project XX for issue types Epic, Story and Bug (also visible in field configs).

I was wondering if it may be due to the rather complicated JQL that advanced roadmaps is missing on those fields....

Best regards, Alessa


author: Dave
body: Thanks [@Alessa Jaeger _LSY_](/t5/user/viewprofilepage/user-id/3902055) - so just to confirm, you can see (and set) those "Planned Start" and "Planned End" fields in the issue screens for issues from all the projects that are loaded into the plan?

Regards,

Dave


author: Alessa Jaeger _LSY_
body: Dear [@Dave](/t5/user/viewprofilepage/user-id/1183605) ,

I actually found the error - the "issuefunction in subtasksOf" fetched ALL subtask issue types, although we only use one. For those, I didn't add the date fields to the screens.

Thanks for your effort! :)


Tags: advanced-roadmaps

server
I'm having major performance issues with Advanced Roadmaps. Any ideas?
Asked by andrew.ching:

I'm having major performance issues with Advanced Roadmaps. It appears to have started when the views were added. Users are reporting errors and data not loading quite frequently - any ideas on why this has slowed down so much and if there are any moves to make improvements?


Answers:
author: Roi Fine
body: Hi Andrew,

Sorry to hear you are experiencing this issue. It would be great if you could raise a support ticket [here.](https://support.atlassian.com/contact/#/)

One of our engineers will try to help you out.

Thanks,

Roi \| Product manager


Tags: advanced-roadmaps

cloud
Updating Board Query to include Epics
Asked by Abbie Skelly:

I would love some guidance on updating a board query to include epics from another project, in order for the epics to display properly in Roadmaps.

Currently the board filter does not have this in place and I do not want to mess up the current view. It pulls in stories within this project that do not have epics and do.

Any guidance on how to write the jql for this. Do I need to put in the specific epic links for each one I want to pull in or is there an umbrella term I can use to pull any epic in that is within this board?


Answers:
author: Dave
body: Hi [@Abbie Skelly](/t5/user/viewprofilepage/user-id/4157521) ,

First I just wanted to confirm that you're using Advanced Roadmaps (and not just Roadmaps)... if you are using Advanced Roadmaps then our usual recommendation would be that you have 2 issue sources - one for each project. However, you could just have one for cross-project JQL filter as an issue source.

However, I noticed that you're specifically asking about having both in a board. This is also pretty straightforward as you can just create a JQL filter for both projects and then create a new board for a project and use that filter. For example, a filter might look like this:

```
project = "Another Project" AND issuetype = epic OR project = "Example Project" AND issuetype = Story
```

When you create the board you choose the project you want it to live in.

I hope that helps!

Regards,

Dave


Tags: advanced-roadmaps

cloud
I cannot see the "plan" option in my tabs.
Asked by lisa:

For some reason I cannot see the "plan" option in my Jira overview. Anyone have an idea why?

![Screenshot 2020-11-15 at 10.18.43.png](https://community.atlassian.com/t5/image/serverpage/image-id/118331iC8892185F54D5189/image-size/large?v=v2&px=999 "Screenshot 2020-11-15 at 10.18.43.png")


Answers:
author: Walter Buggenhout
body: Hi [@lisa](/t5/user/viewprofilepage/user-id/4161064),

Advanced roadmaps is a feature of the premium plan in Cloud. Maybe you are on a different plan?

Have a look at the different plans and their features here: <https://www.atlassian.com/software/jira/pricing>

comments: author: lisa
body: thank you!

I just upgrade to premium trial ;)


author: Paul O
body: Did you have the option previously?

The option won't appear if you aren't on Jira Premium. See [this post](https://community.atlassian.com/t5/Jira-Software-questions/No-quot-Plans-quot-tab-for-Advanced-Roadmaps/qaq-p/1423616)


Tags: advanced-roadmaps

cloud
Epics not displaying in roadmap
Asked by Abbie Skelly:

I have one specific roadmap that I am having trouble with.

I cannot get the epics to show up in the roadmap view, only the stories are pulling through. During the roadmap set up, I choose the board and in the set up flow it is noted that there are no epics. But there are epics associated with each task. Ive also tried creating a filter view of the epics/stories I want to pull in and use that as my foundation. The epics still do not pull through.

The epic(s) these stories are using originate from another kankan board, perhaps that is the issue? Any help or guidance would be appreciated.


Answers:
author: Joseph Chung Yin
body: [@Abbie Skelly](/t5/user/viewprofilepage/user-id/4157521) - If you setup your AR plan (input source from the board), then the board itself must have the board filter query to include the Epics from another project or correctly pull in the epics from the same project.

Keep in mind that a Jira board (Scrum of Kanban) can include content from one or more projects.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSD Functional Lead, Global Infrastructure Applications Team

Viasat Inc.


Tags: advanced-roadmaps
Epic Siblings Not Appearing In Advance RoadMap
Asked by tyrone kimble:

Epic (CFAV-574) is assigned to FINIT-1 parent (initiative) but is not appearing in roadmap under assigned parent (initiative)...

![Initiative Contents.png](https://community.atlassian.com/t5/image/serverpage/image-id/117440iD25984BB73181CB3/image-size/large?v=v2&px=999 "Initiative Contents.png")

![Epic To Initiative Assignment....png](https://community.atlassian.com/t5/image/serverpage/image-id/117439i79EF8A064BED6411/image-size/large?v=v2&px=999 "Epic To Initiative Assignment....png")

Epic 574 is assigned to FINIT-1 (see above) but does not appear in Roadmap. Both 577 and 574 epics have exact same parameters (fixed versions, etc).

Using both project and project kanban board for roadmap issue source. Any ideas???

Thanks...

![Initiative To Epic.png](https://community.atlassian.com/t5/image/serverpage/image-id/117436i710014B2FEF9CE52/image-size/large?v=v2&px=999 "Initiative To Epic.png")


Answers:
author: Dave
body: Hi [@tyrone kimble](/t5/user/viewprofilepage/user-id/3867320) ,

If all other things are truly equal (fix versions, status, etc) and the epics are both appearing on that Kanban board then you might want to double check your issue source configuration to make sure that you haven't accidentally excluded the epic from the plan.

You seem to have examined the most likely reasons for a plan being missing:

* issue source configuration
* workflow status / completed issue inclusion configuration
* assigned fix version not being included in the plan

If it is none of these things and the issue is not excluded from the plan intentionally then I'd reach out to support for assistance,

Regards,

Dave


Tags: advanced-roadmaps

cloud
Advanced Roadmaps - Issue Source - Board - Scrum Board - Not showing all Issues
Asked by Mike Lemmon:

Hi There .. thanks for all of the support the community has provided, much appreciated.

At the moment I'm trying to setup a plan in Advanced Roadmaps, using an Issue Source of Board - being our teams Scrum Board.

When I check what is being displayed on the Roadmap, it is missing User Stories that are in the Sprints in our teams backlog.

When I go back through the Issue Source, and drill down through the Epics, to the User Stories, the missing User Stories do not show here either.

Any thoughts on why the User Stories on my Scrum Board / Backlog are not showing into my Plan?

I look forward to receiving informative responses, like before.

Thanks again, have a great day.


Answers:
author: Mike Lemmon
body: Ah... found it ..when doing the Issue Sources, you need to select the Version that each of the User Stories are in, otherwise the User Story will not appear in your plan!!

comments: author: suruchi bharati
body: Mike, for us in issue sources we have selected specific releases. So only issues tagged with those releases in Fix version field should show up in plan. but this isnt working. several issues that have the selected releases marked in project do not show up. And several issues that do not have selected releases marked show up.

Did you face similar issue


Tags: advanced-roadmaps

board

issue

scrum

server

source
performance issues loading plan
Asked by marie.mogridge:

Over the past few days we have noticed a significant drop in performance when loading the Advanced Roadmap Plan  

This is causing my team significant distress

Please can you confirm what is causing this issue?


Answers:
author: Dave
body: [@marie.mogridge](/t5/user/viewprofilepage/user-id/3931312) , [@chris.reyes](/t5/user/viewprofilepage/user-id/3182988) - We'd recommend that you reach out to <https://support.atlassian.com/contact/> so that we can better look into these issues. It's likely to yield a faster resolution than via these community posts.

Regards,

Dave

comments: author: marie.mogridge
body: [@chris.reyes](/t5/user/viewprofilepage/user-id/3182988) - I've logged a support ticket   

PCS-20921


author: chris.reyes
body: Same here. Almost unusable. When you first open it, it can take 2-3 minutes to load the plan.

comments: author: Gonchik Tsymzhitov
body: +1


Tags: advanced-roadmaps

cloud