youngmon/atlassian-qna huggingface dataset:
Advanced Roadmap not showing issues that are Done
Asked by Kelly Strand:

I am having the issue with my Advanced Roadmap. No issues that are Done are showing. I've tried Resolution of Done and Resolved. The issues have a resolution date. I have the the Completed Date Filter set to 3 months back (all my completed issues have a date earlier than that).

The issues are showing up on my boards, as well as in separate queries.

I've looked through all the comments on this topic and cannot find anything that resolves my issue.

Any other suggestions?


Answers:
author: Joseph Chung Yin
body: [@Kelly Strand](/t5/user/viewprofilepage/user-id/3956832) - You should check the following area:

1) In your AR plan, access the configuration and "Issue Sources" and make sure your "Completed Issues" setting is correct. By default it is set to 30 days. If your issues in your plan were closed/done prior 30 days ago, then those issues will be dropped off from your plan.

You can change the settings to longer then 30 days if you needed. As recommended that showing too many completed issues in your plan may impact your plan's performance. Lastly, you cannot set this setting to 0.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSD Functional Lead, Global Infrastructure Applications Team

Viasat Inc.


Tags: advanced-roadmaps

server
Portfolio Completed Issues Days not saving
Asked by larry joseph:

In the Improved Interface we are trying to get it to show some completed issues. I found on the Configuration \> Issue Sources screen a field that it lets you choose how long any completed issue will show on the plan. Problem is it doesn't retain my changes to the value. It seems set at 30 days and you can click the up/down arrow in the field to change it, but if you leave the screen and come back, it's reset back to 30. Is this a bug, permission issue, Admin issue, user error....?

See <https://confluence.atlassian.com/jiraportfolioserver/issue-sources-967895168.html>

See attached screen shot

![Completed Issues Bug2.png](https://community.atlassian.com/t5/image/serverpage/image-id/113774i3465D564E6485453/image-size/large?v=v2&px=999 "Completed Issues Bug2.png")


Answers:
author: Mark Davies
body: Hi [@larry](/t5/user/viewprofilepage/user-id/4032170)

This does sound strange. When you change the value in the textfield from 30 days, make sure you click outside the textfield before leaving the page. Otherwise it might not be updating this change.

Cheers

Mark

comments: author: larry joseph
body: Thanks for suggestion. I got it to work, but not by clicking off. I found that if I use up/down arrows to change value I have to click into the field before the change is recognized. I also had some odd behavior previously trying to click into and type the value. So there is something odd about how the field works (wonder if browser issue?), but I got it to take the new values. Thanks.


author: Joseph Chung Yin
body: [@larry joseph](/t5/user/viewprofilepage/user-id/726277) - Glad it worked for you. Try it by entering the value without using the up/down arrows, then simply click on "back to plan". The changed value should also be retained as I described in my previous answer.

The odd part is that in our env, we don't see the up/down arrow. BTW we are using Chrome to access Jira/AR.

Best, Joseph


author: Joseph Chung Yin
body: [@larry joseph](/t5/user/viewprofilepage/user-id/726277) - We are using Jira DC 8.9.1 with AR 3.29.1 (On Prems). In our env, we don't have the up/down arrows to change the days. We enter the value to adjust the default 30 days setup. All we have to do is to go back to the plan "Back to Plan" and the value is saved.

The only time where change will revert back to the default setting if we set it to 0 day.

You may have to submit a formal support request with Atlassian Support Team as there may be a bug in the AR Cloud version.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSD Functional Lead, Global Infrastructure Applications Team

Viasat Inc.


Tags: advanced-roadmaps

server
include a recently closed epic in the portfolio
Asked by Incognito AM:

I am trying to include an Epic in the Jira Portfolio. It is closed less than a month ago and even though I set "completed days" to 180, still the epic does not appear in the roadmap.

The epic appears in the filter, but not in the portfolio.  
I tried and reopened the epic, it appeared in the portfolio!

![Completed days (Issue sources).PNG](/t5/image/serverpage/image-id/113484i2FA44EC31D35E9ED/image-size/large?v=v2&px=999 "Completed days (Issue sources).PNG")![Jira Filter.PNG](/t5/image/serverpage/image-id/113485iA95F73F112A6DA4F/image-size/large?v=v2&px=999 "Jira Filter.PNG")![Jira Portfolio.PNG](/t5/image/serverpage/image-id/113486i6EB43F5F25B94342/image-size/large?v=v2&px=999 "Jira Portfolio.PNG")![Portfolio source scope.PNG](/t5/image/serverpage/image-id/113487i279D48CCEA414468/image-size/large?v=v2&px=999 "Portfolio source scope.PNG")


Answers:
author: Joseph Chung Yin
body: [@Incognito AM](/t5/user/viewprofilepage/user-id/4118209) - What is your EPIC Status (NOTE this is not the WF Status of the issue) for TPMMAN-1458? If the EPIC Status is set to DONE where your user has mark this EPIC as DONE in his/her board, then it will not show up in your AR plan.

In other case, if the EPIC above was already "CLOSED", then you build your plan **afterward**, then it will also not show up in the AR plan.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSD Functional Lead, Global Infrastructure Applications Team

Viasat Inc.


Tags: advanced-roadmaps
fixed issue start dates and auto-schedule
Asked by Craig A:

How do I fix a hard start date to an issue that wont be overwritten by Auto-schedule.

Example-

I have an issue that cannot be started until 10/15, because parts will not be in house.

How do I force advanced roadmaps to respect that date even when I auto schedule?

For reference, I'm have the exact issue explained here

<https://community.atlassian.com/t5/Advanced-Roadmaps-questions/Fixed-start-date-requirement-in-auto-scheduling/qaq-p/1384682?tempId=eyJvaWRjX2NvbnNlbnRfbGFuZ3VhZ2VfdmVyc2lvbiI6IjIuMCIsIm9pZGNfY29uc2VudF9ncmFudGVkX2F0IjoxNjAyMTc3Mzk1NTQ4fQ%3D%3D>

Thanks in advance.


Answers:
author: Bernhard H_
body: Unfortunately, for whatever reason, Atlassian removed the feature "Earliest Start Date" from the new planning interface.

Next to switch back to the old planning interface (old name Portfolio4JIRA), as a workaround, you can try to assign the second story to a release which has the intended fixed start date as start date of the release. Then, according to the documentation, the auto scheduler starts the calculation of the story at the start of the release.

comments: author: Bernhard H_
body: Hi all,

I found a service request <https://jira.atlassian.com/browse/JPOSERVER-2563> which requests to bring back the former "Earliest Start Date" feature to the new interface. Please vote for it if you are interested in getting it back. It should help to solve your (and honestly my) problem.


author: Yves Tellier
body: Same for me


author: minhtrietbkit
body: I too have this problem


Tags: advanced-roadmaps

cloud

start-date
Showing Risk Status at an Initiative Level
Asked by Clare Chawke:

Hello  
I have an Advanced Roadmap Plan based on multiple Initiatives from multiple teams. It looks great and nicely rolls up the status to a high level.  
One thing we're missing is a "Risk Status" to say if the whole initiative is at risk. On a traffic light scale, Red/Yellow/Green. I can add a field to the Initiative for this status but I don't know how to display this nicely in Advanced Roadmaps. Either with a color or a tag that jump on at a quick glance.

Anyone implemented something like this? In RTC we used to have plans where you could add color tags based on labels or fields to quickly highlight status. Everything that was green was good. Anything that was Yellow/Red got drilled into.


Answers:
author: Kiran Mitra
body: I am also in need for a solution that visualizes, sorts, filters advance roadmap plan groups/initiatives based on risks, with the option to record and manage risks.


Tags: advanced-roadmaps
Completed issues are not populated in Plan view
Asked by Ra?l Fern?ndez Fraile:

I have several Plan Project in my Jira and I can't see any completed issue within the Plan view where all issuetype hierarchy is shown. Even though I set in the Plan configuration the number of days after the completion to 200 as you can see in the picture below:

![Capture.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/113472i5BA4A97A78DEE590/image-size/large?v=v2&px=999 "Capture.JPG")


Answers:
author: Joseph Chung Yin
body: [@Ra?l Fern?ndez Fraile](/t5/user/viewprofilepage/user-id/307041) - As stated by [@chris.reyes](/t5/user/viewprofilepage/user-id/3182988)

Essentially in Jira the resolution field should not be NULL (it shows up as "Unresolved" - internal representation of NULL for the field) for completed issues. You may also need ensure your plan's issues sources are setup properly.

If you set your issue sources against a board (i.e. SCRUM or KANBAN), then your completed issues WF statuses need to be located at the last right column (terminal column). Otherwise, those issues will never be truly "COMPLETED" in the Jira system. Example, if you try to close out a sprint where those issues are not in the status associated in the last right column, then Jira will ask you to move those issues to another future sprint or the backlog.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSD Functional Lead, Global Infrastructure Applications Team

Viasat Inc.


author: chris.reyes
body: Make sure you're completed issues "Resolution" is set to "Done". Closed issues where the resolution field is not set to "Done" do not appear on Plans.


Tags: advanced-roadmaps

cloud
Global permissions needed to view a plan in Advanced Roadmaps?
Asked by Anna Prostrollo:

We have had Portfolio for quite some time, and I had set up some users to have plan-specific permissions. They didn't have Portfolio global permissions - just permissions to view/edit specific plans. It has been working fine until recently. I know that recently everything shifted to Advanced Roadmaps. Now, the users that could access specific plans can no longer access them.

They don't see a Plans option on the top menu (like I can as an admin), so they were trying to use their bookmarked URLs to go directly to the plan. I even navigated to the plan and sent them the URL from my address bar in case there was an issue with their bookmark. In all cases, the page that loads is blank and has a pop-up that says, "Something's gone wrong. Our team has been notified. If the problem persists, please contact Atlassian Support."

In addition, I created a new test plan based on a single board (with a classic project, not a next-gen project) that they have access to. It's using the old UI instead of the new UI. They can't access this new plan either.

In all cases, the plans load fine for me. I also tried logging in as the users, and I saw the same thing that they're seeing, so I know it's user-specific and not something in their browsers or on their laptops.

Did permissions change (from how they worked in Portfolio) with the rollout of Advanced Roadmaps such that users have to have global Advanced Roadmap permissions in order to access plans? If so, does that mean that I can no longer limit plan visibility so that users only see the plans they should have access to?

-----------

UPDATE: As of today (10/14/20), if the users attempt to access the plans, they no longer get the "Something's gone wrong..." message. Instead, the page says, "Access to plan denied. Ask the owner to grant you access to this plan." I even removed a user as a plan editor and added him back into the list of plan editors, and that still didn't resolve it.


Answers:
author: jbarr
body: Same issue here... anyone from Atlassian?


Tags: advanced-roadmaps

cloud

permission
Custom field values are still available in my plan
Asked by Laura Gerlev Hansen:

Hi community!

I have a Jira Server instance with the addon Advanced Roadmaps for Jira.

I've created a number of custom fields, which I show in my Plan.

The trouble is that I have some "select list (single choice)" custom fields, where I have disabled some options, but these options are still possible to choose from the plan view.

If I edit the issue directly in the Jira project, it only shows values which are still enabled, but in the plan view I get all options, even if they shouldn't be possible to choose.

We have done a re-index of our instance since disabling the values.


Answers:
author: Lasse Langhorn
body: Hi [@Laura Gerlev Hansen](/t5/user/viewprofilepage/user-id/4014935) and [@Joseph Chung Yin](/t5/user/viewprofilepage/user-id/396739)

I have submitted a request to Atlassian support.

I will let you I they can confirm and reproduce this bug.

Regards

Lasse Langhorn


author: Joseph Chung Yin
body: [@Laura Gerlev Hansen](/t5/user/viewprofilepage/user-id/4014935) Hi Laura - We have also reproduced your issue (We are on Jira DC 8.9.1 with AR 3.29.1). I would recommend you to submit a support case with Atlassian support for further assistance. It seems it is a bug in AR.

[@Dave](/t5/user/viewprofilepage/user-id/781587) - Atlassian are you aware of this reported issue with AR?

Best, Joseph Chung Yin

Jira Functional Lead, Global Infrastructure Apps Team

Viasat Inc.

comments: author: Laura Gerlev Hansen
body: Hi [@jtyetukuri](/t5/user/viewprofilepage/user-id/26829)

Thank you for the help! I'll reach out to Atlassian support.


author: Dave
body: Sorry for the slow response [@Joseph Chung Yin](/t5/user/viewprofilepage/user-id/396739) - I was not previously aware of this issue - it looks like this has been raised as this bug: <https://jira.atlassian.com/browse/JPOSERVER-2871> - I'll aim to get this on our short term roadmap to be fixed.


Tags: advanced-roadmaps

server
Done epic's don't appear in roadmap view
Asked by Julien BIAUCE:

Hi,

I use the beta "road map" on classic jira project.

My Kanban filter is really simple (only on the "Project")

I don't have sub filter rules, don't hide olds issues.

When my epic pass to the status "Done", it appear in the roadmap view with the green picto "done". If i refresh, the epic no more appear.


Answers:
author: Stella Mihovska
body: Same issue here.  
I have initiatives with several epics - and the Epics marked as Done disappear. Thus the progress on Initiative level is wrong...

Seems by design.

So I'm curious on the answer here as well.


author: Simon Godard
body: Same problem here. We are using Roadmap BETA with Classic project and as soon as we mark our Epics as Done and change their status to Closed, they disappear from the Roadmap view.

We tried to follow the guidelines here ![2020-12-16_12-38-12.png](https://community.atlassian.com/t5/image/serverpage/image-id/122389i49EFACCFF0D67081/image-size/large?v=v2&px=999 "2020-12-16_12-38-12.png")![2020-12-16_12-47-08.png](https://community.atlassian.com/t5/image/serverpage/image-id/122390iB4732F21BB3307A5/image-size/large?v=v2&px=999 "2020-12-16_12-47-08.png")


author: Niranjan
body: Hi [@Julien BIAUCE](/t5/user/viewprofilepage/user-id/2905247) ,

Have you added fix version in your Epic?

comments: author: Julien BIAUCE
body: No i don't manage fix version for my epics


author: Niranjan
body: Hi,

I believe that Epics need to have fix version. Can you update fix version on one of the epics and check if that shows up on the plan

<https://confluence.atlassian.com/advancedroadmapscloud/configuring-the-scope-view-998651442.html>

Try one of the following steps to make your issues appear in your plan:

1. Make sure the **fixVersion** field is not hidden for that issue type.
2. Check if there are any **view filters** configured for your plan that exclude the issues not appearing.
3. The issues not appearing may not have been given a **resolution value**, such as unresolved.
4. The issues may have already been completed.
5. The issues may be within a release that's excluded from your plan.
6. The issues were manually excluded when creating your plan. For instance, when you exclude an epic during plan creation, the child stories of that plan are also excluded.


author: Julien BIAUCE
body: Thank's Niranjan,

Even with a fix version, Epic don't appear in the roadmap.

I don't have the option of the link above. I do not use "advanced projet" but classic project with beta road map version (could be a part of the problem ?)

I think my solution could be in step "4" : The issues may have already been completed

If y change the status of the epic to a "to do" status, it appear in the road map again...


Tags: advanced-roadmaps

cloud
I set up my plan based on filter but the plan does not pull all items?
Asked by Zsofia Kope:

We are using plan and is not pulling all Initiatives into the plan that my filter does? IN MY FILTER I HAVE 76 ITEMS but my plan shows only 30?


Answers:
author: Niranjan
body: Hi [@Zsofia Kope](/t5/user/viewprofilepage/user-id/4086913) ,

I believe that you are using the filter query as a data source of your plan. Could you confirm the settings from your Issue sources of your plan "How long completed issues will be shown in your plan?"

<https://confluence.atlassian.com/advancedroadmapscloud/issue-sources-998651043.html>

comments: author: Zsofia Kope
body: I can set the time. The issue is that is clearly pulling subtasks associated with the stories that are to to or left in progress etc.

Whether I change 30 days or 90 days my unestimated issue count is the same (subtask and stories lumped together) . we do not estimate subtasks so is pulling all of them in :(.


author: Zsofia Kope
body: JIRA considers subtask te same as any issuetype and that is the issue. I plan we should be able to choose what issuetype needs to be rolled up to initiaitive + epic level. WE dod not have that flexibility. so my executivesare flipping because does not give the accurate unestimated stories z(since adds subtasks:()


Tags: advanced-roadmaps
Unable to add custom fields in roadmap
Asked by Surya Kamepalli:

In the advanced roadmap, I am trying to add an additional column (custom field that already exists)

Here are the steps I followed

1. Selected the Configure option for the Roadmap

![Custom field 3.png](/t5/image/serverpage/image-id/113306iD39E5AB2A1128FC3/image-dimensions/506x169?v=v2 "Custom field 3.png")

2. Under Source Data options on the left side, I selected the custom fields option by selecting the hyperlink: adding custom fields

![custom field screen shot 2.png](/t5/image/serverpage/image-id/113307i276371E14C127145/image-dimensions/772x269?v=v2 "custom field screen shot 2.png")

3. I searched for the custom field "Story Type" and chose the option "Add 1 field". But, nothing happens after I add this and I still cannot locate this field as an option in the fields option in the plan. Am I doing this right?

![Custom Field screenshot 1.png](/t5/image/serverpage/image-id/113303iADD95754C1969F5F/image-dimensions/564x218?v=v2 "Custom Field screenshot 1.png")


Answers:
author: Surya Kamepalli
body: I was able to get this resolved. This is related to permissions to Advanced Roadmap

comments: author: Gary Fitzgerald
body: Hi Surya,

I have the same problem. Please explain in more detail how you got it to work.

Thanks

Gary


author: Niranjan
body: Hi [@Surya Kamepalli](/t5/user/viewprofilepage/user-id/4116893) ,

What is the field type of "Story type"?

comments: author: Surya Kamepalli
body: [@Niranjan](/t5/user/viewprofilepage/user-id/715719) Thanks.

Field type - Select list (Single choice)


author: Niranjan
body: Hi [@Surya Kamepalli](/t5/user/viewprofilepage/user-id/4116893) ,

It works fine in JIRA server. I believe that you are experiencing an issue related to the bug - <https://jira.atlassian.com/browse/JSWCLOUD-19140>


author: Surya Kamepalli
body: Hi [@Niranjan](/t5/user/viewprofilepage/user-id/715719)

Thank you. We are not using the cloud instance and this is the Server edition.

The ticket you shared seems to be about column sizing. My issue is around adding a custom field column to the roadmap view. The custom field already exists and the teams have been using this. The roadmap will not serve its purpose if we are not able to see this particular field.


author: Niranjan
body: [@Surya Kamepalli](/t5/user/viewprofilepage/user-id/4116893) - What is the version of your plugin? Can you try creating a new plan, with the different set of issues that has values for Story type? Just want to ensure if the issue is project specific.


Tags: advanced-roadmaps
Epics from Jira Project not visible in Plans
Asked by Khan, Utsav:

I have many epics defined in my Jira project, and all of them have connected stories. But when I look into plans some of the random epics even if they are **In Progress** does not appear on Plans.

The stories linked to those epics appear as **issues without parent** but I have checked many times that these stories have Epics linked.

Could not find a fix for this, tried different Plans settings but no effect, any resolution to this issue is highly appreciated.


Answers:
author: Niranjan
body: Hi,

What is the data source of the plan? If that is board - What is the filter query used by the board? Does your filter query include Epics in it?


Tags: cloud

epic

plan
Jira Portfolio - Configuring Hierarchy Levels - Epic and Story
Asked by Steffen Schuchardt:

Hi,

in this Documentation is a Screenshoot which shows that Epic and User Stories can be assigned to different Hierarchy Levels, so that User Stories can (from a Hierarchy Level view) put underneath Epic but separated and put above all other Standard Tasks.

[Jira Portfolio Server 0318 - Configuring Hierarchy Levels](https://confluence.atlassian.com/jiraportfolioserver0318/configuring-hierarchy-levels-986880858.html "Jira Portfolio - Configuring Hierarchy Levels")

In our Installation (Server Version 03.20) there is no possibility to adjust Hierarchy Level for User Stories in a way that they are below Epics. Epic Level is predefined with Ticket Type Epic (grayed out) and can't be changed.

I do have only the option to add User Stories to this Level on top or create a Hierarchy Level for User Stories higher than Epics - which does not really makes sence.

Any Ideas/Hints out there?

best regards, Steffen


Answers:
author: Steffen Schuchardt
body: Seems that just the Hierarchy Level is named "Story" and contains all Standard Issue Types, including Tasks.

comments: author: Dave
body: This is correct - each hierarchy level has its own name, but you can rename the hierarchy level from "Story" to something else if you'd prefer. You do this from the hierarchy configuration page:

![Screen Shot 2020-10-15 at 11.43.48 am.png](https://community.atlassian.com/t5/image/serverpage/image-id/114341iEB098074937EEFBD/image-dimensions/513x283?v=v2 "Screen Shot 2020-10-15 at 11.43.48 am.png")


Tags: advanced-roadmaps
It this feature available in Advanced roadmaps for cloud ?
Asked by Razvan Pop:

Actual screen

![Screenshot 2020-10-02 at 13.02.51.png](https://community.atlassian.com/t5/image/serverpage/image-id/112748iD03E70A08C5E7F18/image-dimensions/448x286?v=v2 "Screenshot 2020-10-02 at 13.02.51.png")

I can't seem to find the ability to edit future sprint capacity. is this available only in Jira server?![Screenshot 2020-10-02 at 15.35.27.png](https://community.atlassian.com/t5/image/serverpage/image-id/112747i7725CCBC6916ACB9/image-dimensions/509x375?v=v2 "Screenshot 2020-10-02 at 15.35.27.png")


Answers:
author: Patricia Francezi
body: Hi [@Razvan Pop](/t5/user/viewprofilepage/user-id/3928264)

Advanced roadmaps are available from Jira Software Premium plans in cloud instances.

This is not available for standard, nor Server.


Tags: advanced-roadmaps

cloud