youngmon/atlassian-qna huggingface dataset:
Incomplete issue source data
Asked by Wessel Kamphuis:

Jira roadmaps fails to import all issue from Jira into Jira roadmaps. How can I make sure that all relevant issues are being imported into roadmaps? It is not being caused by any exclusion rules.

Thanks.


Answers:
author: Matt Budnyj
body: Hi [@Wessel Kamphuis](/t5/user/viewprofilepage/user-id/4900777)

If this is Jira Cloud Premium, there is a limit of 5,000 issues and 100 projects for a single plan. See this Atlassian article [linked here.](https://support.atlassian.com/jira-software-cloud/docs/limits-on-plan-size-in-advanced-roadmaps/)


author: Joseph Chung Yin
body: [@Wessel Kamphuis](/t5/user/viewprofilepage/user-id/4900777) -

Welcome to the community. I would recommend you to evaluate your "Issues Source" configuration of your plan to determine what issues are missing. If you can identify the missing issues and provide more details to us, then we can conduct further review and assist you better.

Without more details, it is very difficult to provide you with our suggestions.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.


Tags: advanced-roadmaps
How to Update RAG Status and Quick Status in Roadmap, and update the corresponding Stories
Asked by Monika:

Am updating RAG Status and Quick Status in the Jira Roadmap for my Epics and Stories, but neither of the fields get updated back to the Story when I click "Review Changes". Is there a trick to this or does this just not work ?

Also, some members of my team are unable to edit those 2 fields even though I have given them permission to do so (under Configure, Access Control, Permissions). Is there something special I need to do so that they can edit these fields ?


Answers:
author: Suvarna Gaikwad
body: [@Monika](/t5/user/viewprofilepage/user-id/4835924) Hi Monika

Welcome to Atlassian Community!

Any changes done on JIRA roadmap won't get synced to JIRA unless you **accept** those changes **on Review Changes page.**Also please make sure before you click on Accept changes on Review Changes page, only required changes are checked on Review Changes page.

Hope this helps!

comments: author: Monika
body: Hello [@Suvarna Gaikwad](/t5/user/viewprofilepage/user-id/4541591)

thank you for your response. I don't actually have an "accept" capability on the Review Changes page. I can select the changes I want to have updated, and the program does something, and then says "Success". So it seems like it works, but when I then review the individual Story, the update is not there.


author: Suvarna Gaikwad
body: [@Monika](/t5/user/viewprofilepage/user-id/4835924) Is it possible for you to paste screenshot of Review Changes page after you have made some changes to fields in roadmap?


author: Monika
body: Yes of course :-)

please see attached. I have shown the page, then that it was "successful", but on looking at the Jira story, it hasnt been updated.![Review pages 1.gif](https://community.atlassian.com/t5/image/serverpage/image-id/195397iF360CF0C16D6E16B/image-size/large?v=v2&px=999 "Review pages 1.gif")![Review pages 2.gif](https://community.atlassian.com/t5/image/serverpage/image-id/195398iD4CEB62DF9998BD8/image-size/large?v=v2&px=999 "Review pages 2.gif")![Review pages 3.gif](https://community.atlassian.com/t5/image/serverpage/image-id/195399i3B772B048B189532/image-size/large?v=v2&px=999 "Review pages 3.gif")


author: Monika
body: Hi,

Does anyone have an answer to this please ?

thank you !


author: Monika
body: If anyone is following this, I have found that the fields do display on the "backlog" view, in the side panel. Mind you, the fields can only be viewed and not edited in this view. To update, you still need to do this in the Roadmap.


Tags: advanced-roadmaps
Story Points and Estimates (H) field
Asked by Shiau Chin Teo:

Hi All,

I am using 'Story Points' as estimation in my Jira board.

I am exploring in Advanced Jira Roadmap the field 'Estimate (H)' which seems to be converted automatically based on story points entered for issue type. Is there such setup and if yes how can i see that conversion/relationship? If not what is the relationship between Story Points and Estimates (H) fields.

Thank you.


Answers:
author: Joseph Chung Yin
body: [@Shiau Chin Teo](/t5/user/viewprofilepage/user-id/4838538) -

Welcome to the community. In the old AR for Jira interface UI, you have the ability to define the your own SP to Hr exchange table, however in the new AR for Jira this function has been removed. I believe the main reason is "story points are not hours."

It is not simply a calculation of 1 SP to multiple of hours. Example, some team's 1 SP can be 8 hours, but another team's 1 SP is 16 hours of work.

I am not aware of any existing backend calculation of automatically converting SPs into Hrs against AR for Jira plan by the add-on since that concept has been removed from the app.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

comments: author: Shiau Chin Teo
body: [@Joseph Chung Yin](/t5/user/viewprofilepage/user-id/396739) , [@Pramodh M](/t5/user/viewprofilepage/user-id/3691224)

Thanks for your reply.

As we are not using the Estimate (H) in Jira and in the Advanced Jira Roadmap, the Estimate (H) field seems to be populated with an exchange pattern based on Story Points, that's why the question.


author: Joseph Chung Yin
body: [@Shiau Chin Teo](/t5/user/viewprofilepage/user-id/4838538) -

You can check your issues (showing in your plan) to see if they also have Time Tracking information related fields enabled and populated. This is why you are seeing data in the plan when you selected the Estimate (H) option in your plan.

You can simply just change the option back to Story Point option in your plan, thus disregards anything with Estimate (H) option since you are not using it.

Best, Joseph


author: Pramodh M
body: Hi [@Shiau Chin Teo](/t5/user/viewprofilepage/user-id/4838538)

Welcome to the community ?

Story Points in Jira is Story Points in Roadmap

Remaining Estimate in Jira is Estimate (H) in Roadmap

There is no relation between them

Thanks,

Pramodh


Tags: advanced-roadmaps
Roadmap filter on components with none selected or Project has none set and criteria is OR not AND
Asked by Linda Chang:

I'm using Advance Roadmap Plan to showcase all the projects done in the Org, which span through multiple Jira Projects. I will create multiple view using the filters for the different teams.

I would like to use the components and labels fields.

With Components I have these 2 issues:

1) How to select tickets in a Jira Project that don't have any components defined in the Jira Project. Default, I would like to pick up all tickets in the Jira Project, but now it show none of the tickets in that Jira Project.

2) If the Jira Project has entries in the Components field, I want to select those have no components selected. Right now can't get that.

With Labels in filters: In the filter, one can select diff criteria for the the diff fields possible in the filter. Right now the logical is AND. I would like the logic to be OR instead. So, for all tickets under the selected Jira Projects OR the label contains "xyz"

Is that possible?

Though my company instance is Server/Data Center, this would apply to Cloud


Answers:
author: Fabian Lim
body: Hi [@Linda Chang](/t5/user/viewprofilepage/user-id/4703900)

With jql advanced searches you can have or statements.link: <https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-939938733.html>

I hope this helps

comments: author: Linda Chang
body: I've familiar with jql adv query as that is how I got the plan up with 1 filter with such query. I was looking at creating diff views for diff sub-teams after that in Advance Roadmap filtering on the fields only. with Fabian answer, I checked out the filter for input source and realized I can reorg and have multiple sources (filters) and for those complex query views/sub-teams I would filter on the source.

Tyvm Fabian and Joseph


author: Joseph Chung Yin
body: [@Linda Chang](/t5/user/viewprofilepage/user-id/4703900) -

Hi Linda:

In addition to what [@Fabian Lim](/t5/user/viewprofilepage/user-id/3131564) mentioned. Because you mentioned the usage of component/labels in your plan's filters. You should be aware of the following bug which is fixed in Jira DC/Server version 8.22 - <https://jira.atlassian.com/browse/JPOSERVER-2957> ("Filtering on a component / label when the plan is grouped by component / label, does not display the expected issues").

Don't know if you already know about this bug or not. If not, hope this helps you when you try to create different plan's views where you use component/labels filtering when grouped by those fields.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.


Tags: advanced-roadmaps

server
Enable capacity planning in Advanced Roadmaps
Asked by Moti Stein:

I read few docs about how to work with capacity using plan/roadmap but I can't see plans menu in Jira on the main top bar, and not any option of plan in the roadmap.

I tried to add the team field to issue field but then I can't choose my team, I get text of:

"plan specific teams can only be selected through a plan" - but I have no plan

I used cloud version with standard plan.

How can I enable it? Is there any plugin to manage the employees capacity


Answers:
author: Dave Mathijs
body: [@Moti Stein](/t5/user/viewprofilepage/user-id/4625701)

If you see a Roadmap tab in Advanced Roadmaps, that's your Plan. A plan is basically a collection of issues in a hierarchy determined by a board, project or filter.

Can you confirm whether you are on Server/Data Center or Cloud (URL ending with atlassian.net)

It depends on the configuration of the plan whether teams in a plan are defined.

comments: author: Moti Stein
body: Cloud.


author: Dave Mathijs
body: Advanced Roadmaps is only available as part of Jira Software Cloud Premium and Enterprise, so not available for Standard.


Tags: advanced-roadmaps

plan
unable to view an initiative in jira advanced roadmap
Asked by Salwa Chamra:

I created an initiative in jira advanced road map and got the following message

**CIC-79 is no longer visible in your plan**

This issue is missing some details that are specified in the issue sources of your plan. To make this issue visible, add these missing details to the issue.

Appreciate it if someone can tell me how to sort this out so that I can view the Initiative in jira advanced road map.

What steps do i need to do?

Thanks heaps

Salwa


Answers:
author: Joseph Chung Yin
body: [@Salwa Chamra](/t5/user/viewprofilepage/user-id/4710423)

You should evaluate your plan's issues source setup assuming you have edit right against the plan in question. If so, access plan's configuration and select the "Issue Source" option to validate your setup.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

comments: author: Salwa Chamra
body: thanks. all sorted


author: Joseph Chung Yin
body: [@Salwa Chamra](/t5/user/viewprofilepage/user-id/4710423) -

Excellent. If my suggestion helped. Please click on Accept Answer when you have a chance. So others can benefit the solution suggested if they have similar issues.

Best, Joseph


Tags: advanced-roadmaps

cloud
Can you use other types of dependencies other than "blocks" or "is blocked by"
Asked by Melissa Marks:

Can you track dependencies in advanced roadmaps other than blocks? We use all of the linked options and i would like to track that in my advanced roadmap.


Answers:
author: Joseph Chung Yin
body: [@Melissa Marks](/t5/user/viewprofilepage/user-id/3856468) -

Assuming you have of the Jira Admin right against your environment, then you can access Jira Administration \>\> Manage apps and locate "ADVANCED ROADMAPS FOR JIRA" section in the left pane \>\> Dependencies option.

In the option UI, you will need to add your issue link type(s) that you want to be available for you to use in the plan and don't forget to save the changes.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

comments: author: Melissa Marks
body: thank you! that worked


author: Joseph Chung Yin
body: Excellent. One last recommendation for you to consider -

You/your team needs to determine a defined business process to educate your users on what issue link type to use under what situation when working with plans. Otherwise, you will loose control of your plans' issues dependency due to too many different issue link types.

Please click on Accept Answer when you have a chance.

Best, Joseph


Tags: advanced-roadmaps

dependency
Issue Hierarchy
Asked by Tony B:

QQ Community:

When Creating a Hierarchy in Jira. Does Initiative Come First and Then Theme, Epic, Story or does Theme come First then Initiative, Epic, Story?

I am getting Different Reponses when Googling this. What is Best Practice?

Thanks


Answers:
author: Joseph Chung Yin
body: [@Tony B](/t5/user/viewprofilepage/user-id/4894722) -

Welcome to the community. As per other's responses, it is completely up to you. You don't even have to use Initiative or Theme, you can name them to whatever it works for your organization.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.


author: Nic Brough -Adaptavist-
body: Welcome to the Atlassian Community!

Technically, it's really up to you how you choose to implement your hierarchy

So, historically, Jira Software has implemented only three layers - Epic -\> Issue -\> Sub-task, and you can have many differently named issue types, and sub-tasks. That obviously translates into Epic -\> Story -\> Sub-task in the names you are using.

Advanced Roadmaps gives you more flexibility - layers up above Epic. The default is

Initiative -\> Theme -\> Epic -\> Story -\> sub-task

But that's not fixed in stone, and the names are totally renamable. Even [their own docs](https://www.atlassian.com/software/jira/guides/roadmaps/advanced-roadmaps) do it differently (Odyddey -\> Initiative -\> Epic -\> Story -\> Sub-task). I've seen initiative and theme reversed in that scheme in places, but what I see most often is something like

Saga -\> Epic -\> Feature -\> Story -\> Sub-task (People rename Epic to feature and then use Epic for the layer above)

The Epic -\> Feature thing there is the (default) nomenclature for the Scaled Agile Framework, so we see it more often than other schemes.

TLDR: do what works best for you!


author: Robert Wen_ReleaseTEAM_
body: Hello, [@Tony B](/t5/user/viewprofilepage/user-id/4894722) ! Welcome to the Atlassian Community!

I've seen Theme at the top, and then Initiative, Epic, etc. But honestly, there's no standard above Epic especially since Epics traditionally aren't time boxed the way stories are.

Hope this helps

comments: author: Tony B
body: Thanks


Tags: advanced-roadmaps

cloud
Jira Data Center Advanced Roadmaps Issue missing
Asked by Kruno:

Heyhey,

I know there are multiple issues reg. this topic but non of the points helped me and I must say after spending now roughly two weeks that it is the best Roadmap Plugin for Jira but it has crazy flaws regards to making clear which and why issues are missing.

I am struggling with multiple missing issues first being that new top level Issues (called Demand) are not visible when they are created unless they reached a certain point in the workflow.

- Fix Version field is setup correct - set visible in the field configuration

- We don't use releases nor teams

![Screenshot 2022-04-25 at 14.46.56.png](https://community.atlassian.com/t5/image/serverpage/image-id/194430i7F14F0592664E940/image-size/large?v=v2&px=999 "Screenshot 2022-04-25 at 14.46.56.png")![Screenshot 2022-04-25 at 14.47.02.png](https://community.atlassian.com/t5/image/serverpage/image-id/194431i271659BF58A4CBC6/image-size/large?v=v2&px=999 "Screenshot 2022-04-25 at 14.47.02.png")

- There is no additional UI Filter set on the Plan

![Screenshot 2022-04-25 at 14.47.50.png](https://community.atlassian.com/t5/image/serverpage/image-id/194432i03E7629F08925F69/image-size/large?v=v2&px=999 "Screenshot 2022-04-25 at 14.47.50.png")

- I x-checked it multiple times and the Issue Source (filter) contains all relevant issues, also this can't be the problem as the issue appears once a certain status is reached

- No status is excluded in the setup

![Screenshot 2022-04-25 at 14.54.30.png](https://community.atlassian.com/t5/image/serverpage/image-id/194436iA86A86DEC377CA5D/image-size/large?v=v2&px=999 "Screenshot 2022-04-25 at 14.54.30.png")

And now here the issue, once pre and once after transitionining from ACCEPTED \> IN PROGRESS. Once the status is IN PROGRESS or DONE the issue is visible, ACCEPTED not. Also, as u can see the Resolution field is available.

![Screenshot 2022-04-25 at 14.48.34.png](https://community.atlassian.com/t5/image/serverpage/image-id/194434iE50D4B06768ED122/image-size/large?v=v2&px=999 "Screenshot 2022-04-25 at 14.48.34.png")![Screenshot 2022-04-25 at 14.48.52.png](https://community.atlassian.com/t5/image/serverpage/image-id/194435i6B9AF9A98672D2B6/image-size/large?v=v2&px=999 "Screenshot 2022-04-25 at 14.48.52.png")

Does anyone have an idea?

Cheers

Kruno


Answers:
author: Kruno
body: Found the solution with the help of this entry:

<https://community.atlassian.com/t5/Advanced-Roadmaps-questions/How-can-I-see-the-Done-issues-in-Advanced-Roadmap/qaq-p/1387004#M4916>

Issues in a "Done" category status need to have a resolution set. Accepted is a status for us which is a mid-done. Well I just changed to "Open" and this fixed it.


Tags: advanced-roadmaps

server
JIRA Advanced Roamap - hierarchy levels
Asked by Michele Poli:

Hi, I've a question related to the hierarchy levels in JIRA Advanced roadmap.

In my project I don't have a fiexd structure (eg. Epic-\>Task-\>Subtask), but I'm working on a business project and I've a not of "non fixed" levels related to business activities.

Can I use only 1 issue type and configure the hierarchy using only 1 type in a "recoursive" way?

e.g.

Issue type = TASK

* Task 1
  * Task 2
    * Task 3
      * Task 4
    * Task 5


Answers:
author: Ming Yin Ho
body: No, you cannot use one issuetype for your hierarchy.  
Each issuetype defines another level in your business.   

<br />

comments: author: Michele Poli
body: Ok, thanks.


Tags: advanced-roadmaps

cloud
Can't Access Advanced Roadmaps
Asked by Brandon Nelsen:

I've been granted access to a team's Advanced Roadmap but find I am unable to access the page. I checked and I have Plan Access but when I try the link I get a notification that I "don't have access to this plan." Thoughts? ![thumbnail_image001.png](https://community.atlassian.com/t5/image/serverpage/image-id/194208i0E336E1C3C637D52/image-size/large?v=v2&px=999 "thumbnail_image001.png")![thumbnail_Image.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/194209i4C643B68E59B73B9/image-size/large?v=v2&px=999 "thumbnail_Image.jpeg")


Answers:
author: Sachithra Dangalla
body: Hi Brandon,

Can you confirm if you have "Advanced Roadmaps User" permissions from "Plans -\> Settings"?


Tags: advanced-roadmaps

cloud
Group by on multiple fields
Asked by Unnikrishnan Ramachandran:

Hello,

I am trying to use the Advanced Roadmaps along with Releases to show a hierarchical structure to my project.

Currently I have the **Group By** on "Release" and it gives me the structure:

![image.png](/t5/image/serverpage/image-id/194237i6DD1404EF990A2FF/image-size/large?v=v2&px=999 "image.png")

I want to **Group By** on 2 fields : Release and Label, to achieve the structure like:

Release 1 --\> Label 1 --\> Epic 1, Epic 2, Epic 3

---\>Label 2 --\> Epic 4, Epic 5

Is this feasible?


Answers:
author: Joseph Chung Yin
body: [@Unnikrishnan Ramachandran](/t5/user/viewprofilepage/user-id/3684190) -

As of right now, it is my understanding that AR for Jira doesn't provide grouping of multiple fields. It is only available for single field grouping.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.


author: Maksim Beliaev
body: Please vote for the feature: <https://jira.atlassian.com/browse/JSWCLOUD-25440>


Tags: advanced-roadmaps
Problem using custom date fields in Advanced Roadmaps
Asked by Andrew Fisher:

We are starting to use Advanced Roadmaps and are bringing in issues from a small number of projects in our system, but are having problems in the "Scheduling" configuration tab when trying to select the custom date fields we want to use.

To elaborate \& provide specifics, we have a large number of different issue types and screen schemes across our projects. However, for our minimal Advanced roadmaps plan, we have an issue source of a filter that brings in only epics from a single project (i.e. "*project = XYZ AND issuetype = Epic*"). We have a custom date fields called "Plan Start Date" and "Play End Date" (which have also been added in the "Custom fields" section of our plan's config).

1. If we configure the "Plan Start Date" field and set its applicable issue types to be just Epics, we're unable to select to use this field in scheduling for our plan - we get the message of "*Make sure to add this date field to all the issue sources of this plan*" (regardless of our plan's displayed hierarchy being set as "epic" to "epic").

2. If we then configure this custom field and set its applicable issue types to be "Any Issue type", then we can now select to use this field in scheduling for our plan.

3. If we configure this custom field to update the applicable issue types, but now manually select all but one of the issue types (the one excluded doesn't seem to matter, and most of the issue types in our system aren't used within our example "XYZ" project's issue type scheme), then we're again unable to select to use this field in our plan scheduling.

So I guess my question is - for custom date fields to be selectable in the Advanced Roadmaps "Scheduling" config, do these fields need to be configured to be associated with all issue types in the system, regardless of which issue types are associated with the issue sources? (I'm hoping we don't have to add these custom fields to all issuetypes in the system if we don't have to, although we may be able to workaround this with careful config management of screen schemes if we have to).

Thanks!


Answers:
author: Daniel Ebers
body: Hi [@Andrew Fisher](/t5/user/viewprofilepage/user-id/510325)

I feel this could correspond to the following bug:

* **The field context configuration prevent Advanced Roadmaps to use it as start/end dates fields**   
  <https://jira.atlassian.com/browse/JSWCLOUD-23423>

While it is targeted to Cloud the content is the same. In case this is what you are seeing also, I would suggest to bookmark the bug report to keep track of the progress.

Cheers,  
Daniel


Tags: advanced-roadmaps

server