youngmon/atlassian-qna huggingface dataset:
How do I fix Jira Sprint Status in Align when it does not match the Sprint Status in Jira?
Asked by Paula Hidalgo:

The Sprint status shown in the Align \> Settings\> CONNECTORS Jira Managment \> Jira Sprints for a specific board does not match the Sprint status in Jira. Example for board ID 1234, Jira Sprint 36148 shows active and Jira Sprint 38890 shows active. The correct status for Jira Sprint 36418 is Closed and Jira Sprint 38890 has the correct status of Active.

I can verify Sprint 36148 is closed in Jira by the API call <https://mycloud.atlassian.net/rest/agile/1.0/sprint/36148> which returns "state": "closed".

The two sprints between these (Jira Sprint 38555 and Jira Sprint 38889) show the correct Jira status Closed.

Any ideas on how to fix the Jira Staus for Sprint 36148?

NOTE: In Jira Software, we do NOT allow parallel sprints for company-managed projects. The project with the wrong Sprint Status is company-managed.


Answers:
author: Allan Maxwell
body: [@Paula Hidalgo](/t5/user/viewprofilepage/user-id/3506387) I assume you have tried this already, but just incase:

To sync Jira sprints on demand:

1. Navigate to **Admin -\> Jira Management**
2. Open the **Jira Sprints**tab.
3. From the **Boards**drop-down menu above the grid, select the board with the sprints you want to synchronize on demand.
4. Click the **Sync Board Now** button.
5. To synchronize sprints for the other boards if needed, repeat Steps 2--3.

comments: author: Paula Hidalgo
body: [@Allan Maxwell](/t5/user/viewprofilepage/user-id/3502714) - Tried Sync Board Now button again just to verify I had clicked that button. Did not work. Should I open a Support ticket?


author: Allan Maxwell
body: [@Paula Hidalgo](/t5/user/viewprofilepage/user-id/3506387) Yes, I would go ahead and open a support ticket. Just out of curiosity, do you see anything in the Connector logs?

1. Navigate to Admin -\> Jira Settings
2. Click view logs (https://**{YOUR COMPANY NAME}** .jiraalign.com/JiraLogReport )
3. Change the drop down to Iterations
4. Search for the the Jira Sprint ID

![Screenshot 2023-11-22 at 8.47.40 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/293218i4F6C65C38734E876/image-size/large?v=v2&px=999 "Screenshot 2023-11-22 at 8.47.40 AM.png")


Tags: cloud
How to do slicing of Epics
Asked by Ruben Stam:

I am looking for a way to slice Epics, and prioritize and track the progress of a slicing level.

In our organisation, Features are tied to components. A combination of features often delivers value, but not all the value delivered by the entire Epic. Negotiations with customers are also often done based on slices.

Hence we are looking for ways to do slicing of Epics and prioritize the slices and track them.


Answers:
author: Allan Maxwell
body: [@Ruben Stam](/t5/user/viewprofilepage/user-id/4132524) Jira Align allows for a work item type to be inserted between Epics and Features. In accordance with SAFe, this work item is typically called a "Capability", but Jira Align allows you to change the name to something like Epic Slice if you like.

comments: author: Allan Maxwell
body: ![Screenshot 2023-11-21 at 3.34.57 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/293063iCA87266679651751/image-size/large?v=v2&px=999 "Screenshot 2023-11-21 at 3.34.57 PM.png")


author: Ruben Stam
body: We've looked at Capabilities but what we run into is that capabilities are then mandatory, also when we would not want to do slicing. Any thoughts?


author: Allan Maxwell
body: While it may initially be a pain for some folks to create a *placeholder* slice, it will have some benefits in the long run: more uniform sizing, creativity in slicing and ease of reporting.  

If you begin your agile journey at the team-level, with Scrum for example, you will quickly find that the meaning of a 3 point Story can vary wildly across your organization. Once you begin to scale agile up to the higher levels it is beneficial to achieve some level of consistency in sizing. SAFe suggests you start with something like 1 point is a person/day but once you get going then "never look back". I think there are advantages to more uniformity in sizing, especially at the Feature level. Introducing Capabilities often has the side-effect of naturally reducing the range in sizes of Features.

It sounds like your slices are tied to components. You may find that introducing slices across the entire organization will lead to more creative use of the concept of slices. One example would be to extend the prioritizing, planning, executing, releasing of Features to areas outside of engineering or IT. For example, many organization do not track how much effort goes into prioritizing the next release of work against all submitted/potential work.

Jira Align reporting is able to work with either slicing or not ...or both. You may be developing your own reports using Enterprise Insights or Atlassian Analytics. Any report above the ART level will be complicated by needing to support a mixed mode with only half the organization using slices.
Advanced Road Map trialling on Cloud
Asked by Roy:

Hi,  
Your help is much appreciated.  
I am looking for a solution to align work (tickets) with organization level categories. Advanced Road Map seems to do exactly that.  

1. Is it available on Jira Cloud ? (premium subscription).  
Market place states that it's only available for Server and Data Center licenses. But this link doesn't have this limitation [Advanced Roadmaps Guide \| Jira Software \| Atlassian](https://www.atlassian.com/software/jira/guides/advanced-roadmaps/overview#what-are-plans-in-advanced-roadmaps)  

2. If it is available on Cloud premium, how do I start a trial?  
thank you


Answers:
author: Antuan Sammak
body: Hi [@Roy](/t5/user/viewprofilepage/user-id/5365746)

Welcome to the Atlassian Community!

1- you are correct, Advanced Roadmap supports Jira Cloud and they are part of Premium subscription only. they are not part of Free no Standard types.

2- to enable them, you need to have admin access on Jira instance then hit settings button from top right corner

select Billing

you will land on a page showing the products you are subscribed to, one of the is Jira Software

click on Manage next to Jira Software

click on Change Plan

Select Premium and follow the steps.

once enabled you will have Premium plan enabled for 30 days free trial.

Advanced Roadmap will be accessible from top menu bar in your Jira, click on Plans.

Hope the above helps.

comments: author: Roy
body: Thank you!


author: Mo Omar
body: Hi there,

We've recently switched over to trial the Premium Plan on our Cloud instance, to trial Advanced Roadmap. However, when I select the available plans as you described in your previous instructions I didn't see 'Advanced Roadmap' anywhere. I've also gone directly to the Market Place page for this app and it still only offers the Data Center/Server option. Could you give us further instructions on how to trial the product?  

Many thanks  

<br />

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

<br />

<br />

<br />

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


author: Antuan Sammak
body: Hi [@Mo Omar](/t5/user/viewprofilepage/user-id/5105093)

as per your screenshot, you are subscribed to Premium plan.

so now you have to head to your Jira instance and from the top navigation bar you should see Plans, or if you are on a small screen then you will see More and upon clicking on it you will be able to see Plans.

once you click on it, i would recommend you to try the option of creating sample plan which should give you a good insights of this feature and how it can be structured and used.

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


author: Mo Omar
body: [@Antuan Sammak](/t5/user/viewprofilepage/user-id/5365045) Thanks for your reply, I've now located where it is. Many thanks for getting back.


Tags: cloud
Show custom Jira fields in Advanced Roadmap Timeline Plan
Asked by Jignesh Jaiswal:

I have enabled the Advanced Jira Roadmap and in Timeline Plan view, only a few fields like Assignee, dates etc. fields are available. How do I show existing fields used in my Jira Project (including custom fields in Jira project associated to the tickets)?


Answers:
author: Tim C
body: Hi [@Jignesh Jaiswal](/t5/user/viewprofilepage/user-id/293622)

*Re: Advanced Roadmaps ....*

To add and view custom fields in your plan:

1. Select **Plan settings** from the left side navigation.

2. Choose **Custom fields** to show you all of the custom fields currently in your plan.

3. Select **Add custom field** in the upper right corner, then search for the fields you want to add.

4. Use the **Add fields** button to finalize your choice.

More details ...

<https://support.atlassian.com/jira-software-cloud/docs/add-and-view-custom-fields-in-advanced-roadmaps/>

There's also a link on there with more information about "Timeline" tool under projects (which isn't direcly connected to 'advanced roadmaps (Plans)')

I hope this helps.

Tim C

comments: author: Jignesh Jaiswal
body: Thanks for quick answer. this worked!


Tags: cloud
Creating Graphs from Roadmap
Asked by Claire Mullins:

Hi Community,

I've recently starting using Roadmaps in JIRA and find it a lot more useful and powerful for my purposes than I had initially expected.

I am using the plan to assign resources across a number of projects from several teams.

I would like to see a simple graph representing my upcoming demand (as planned) to show where there are expected peaks and possible troughs (unlikely!).

Is there a way I can do this without exporting to excel and completing there?

I would prefer to stay in the tool if at all possible.

Thanks in advance


Answers:
author: Marc - Devoteam
body: Hi [@Claire Mullins](/t5/user/viewprofilepage/user-id/5245457)

As far as I'm aware of this is not an option in Advanced Roadmap or even with Jira in any way as Jira is not built for this.

Even on the marketplace there are no apps in relation to demand management.

I think in this topic, you should see to an application that is designed for demand management and if it can possibly integrate with Jira


Tags: advanced-roadmaps

roadmap

velocity
JAR Issue Hierarchy limits in Data Center?
Asked by Adam Parker:

We recently upgraded to Jira Data Center 9.9 and gained access to Advanced Roadmaps.

While setting up the Issue Hierarchy in our instance, we appear limited to a single issue type per level in Data Center; unlike Cloud which allows multiple issue types per level.

In 9.10 and higher, does Data Center get the multiple issue types per level a la Jira Cloud? Or is that flexibility only in Cloud?

Our organization has a hybrid delivery model with both project-orientation on our business side and product oriented on the IT side.

If "Initiative" and "Project" issue types can't both exist as valid at the level above Epic, we will need to find a way to agree on an interim, sub-optimal solution until our organization moves to Jira Cloud in the next 12-24 months.

I have spent several hours reading support articles and YouTube videos and have not yet gotten clarity. Is multiple issue types per level only allowed in Cloud? Is there a more recent Data Center version with this flexibility? Please help me decide whether to invest more time or stop searching.

Kind regards.


Answers:
author: Joseph Chung Yin
body: [@Adam Parker](/t5/user/viewprofilepage/user-id/1462148) -

Hi Adam:

In AR for Jira (Data Center), the issue hierarchy structure allows you to have multiple issue types setup against any level above the Epic in the configuration. Example -

![2023-12-04_6-59-57.png](https://community.atlassian.com/t5/image/serverpage/image-id/295190iD81BA6EC1E2ED241/image-size/large?v=v2&px=999 "2023-12-04_6-59-57.png")

As you can see above - we have multiple issue types (custom standard issue type) associated with the level design above Epic. See reference link - <https://confluence.atlassian.com/display/JIRASOFTWARESERVER/Configure+your+Jira+Software+instance+for+Advanced+Roadmaps>

You are correct that only in Cloud (Premium/Enterprise plan) that one can setup adding additional issue types against the default "Epic" level as documented in <https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/>

Can you clarify on what you mean by not able to have multiple issue types against the level (are you just focusing on trying to add new issue type for the Epic level)?

Please advise and hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

comments: author: Adam Parker
body: I will share your message with our Administrator and see what we find. Thanks, Joseph!


author: Adam Parker
body: [@Joseph Chung Yin](/t5/user/viewprofilepage/user-id/396739) Thank you. Our Administrator was able to make the changes quickly. JAR and hierarchy above Epic are new features for us. Thanks for helping us on our journey!
Viewing availability of team members in JIRA
Asked by Kashyap Vasudevan:

Hi I am using JIRA version 8.20.15 in our organization. I have entered the availability of individual team member following the [instructions](https://confluence.atlassian.com/advancedroadmapsserver/configuring-the-availability-of-team-members-814212629.html#notfound)

What I really wanted was that this availability is reflected in JIRA advanced roadmap "Sprint capacity management" View. But it seems in the road map one could only view/configure Team level availability but not individual team member's availability.

Is there any way I can view the individual team member's availability for all sprints considering his/her vacations/holidays etc?

Thanks in advance!

Kashyap


Answers:
author: Marc - Devoteam
body: Hi [@Kashyap Vasudevan](/t5/user/viewprofilepage/user-id/5375397)

Welcome to the community.

As Jira revolves around teams so does the capacity planning of the Advanced Roadmap.

As you work in a project with multiple users and the work capacity is based on the team and no the individual.

A work around you can make is to have a single user per team in advanced roadmap, you could then view a users capacity.

Otherwise look at Marketplace apps then provide resource planning:

<https://marketplace.atlassian.com/search?query=resource>
Advanced roadmaps showing populated date fields as blank.
Asked by Danish Khullar:

Issues have Target start date and target end date filled, but it is not showing up as blank in Advanced Roadmap. Attaching screenshots as well.![Screenshot 2023-11-21 at 5.46.39 PM (1).png](/t5/image/serverpage/image-id/292988iB81F6A5A9FED7BDA/image-size/large?v=v2&px=999 "Screenshot 2023-11-21 at 5.46.39 PM (1).png")![Screenshot 2023-11-21 at 5.47.08 PM.png](/t5/image/serverpage/image-id/292989i70DF48F024104202/image-dimensions/557x160?v=v2 "Screenshot 2023-11-21 at 5.47.08 PM.png")


Answers:
author: Jean-Emmanuel BANQUEY
body: Hello,

The "EXT" besides Sprint means you have used Project or Filter mode.  
Can you try to import issues in "Board" mode ?  
Or check what you checked here ?  
It is strange you don't see sprint dates in these fields.  
![Capture d??cran 2023-11-21 143629.png](https://community.atlassian.com/t5/image/serverpage/image-id/293005iE2F10165C766BA67/image-size/large?v=v2&px=999 "Capture d??cran 2023-11-21 143629.png")

comments: author: Danish Khullar
body: Hi,

Thanks for the reply. Importing issues in "Board" mode did populate the fields. But it is showing sprint start and sprint end date instead of Target start and Target end date. Issues have Target start and target end date filled but it is not showing that.![Screenshot 2023-11-24 at 12.15.47 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/293531i4B283ECD84C3C535/image-size/large?v=v2&px=999 "Screenshot 2023-11-24 at 12.15.47 PM.png")


author: Jean-Emmanuel BANQUEY
body: Hi,

Yes, if dates are displayed in italic and a "S" is visible like that, it means that they are from the board's sprint.

It's strange but I must admit I have a Jira Cloud instance and I think your screens come probably from a Server/Data Center instance (issue view is really very different at my side).

Can you try to fill dates from Plan, commit changes and check if it's taken in account in the other side ?

But I don't understand why it does not work for you when filling dates from the issue view.
Problem using Auto-schedule in Advanced Roadmaps
Asked by Lynne Cordary:

When using the auto-scheduling feature in Advanced Roadmaps I've experienced two issues: 1) sprints that were green before auto-scheduling are made red. 2) When checking one project to auto-schedule other non-checked projects are changed as well.


Answers:
author: Michael Yaroshefsky - Visor for Jira
body: Hi [@Lynne Cordary](/t5/user/viewprofilepage/user-id/5266832) ,  

Welcome to the Atlassian Community!  

I hope I'm getting your question right. The auto-scheduler for Advanced Roadmaps is there to help you balance out issue dates and capacity. Sometimes, if too much work needs to fit into a sprint, the auto-scheduler might shift some tasks or show a warning.  

**For your first issue, you can try:**   

Reviewing issue estimates  
Adjusting team capacity  
Prioritize issues in another way  

You can also adjust the generated plan to meet your needs. Don't forget everything is based on your plan's settings.   

**Issue 2** is trickier as it may relate to the dependencies in other projects.  

I hope this helps  

comments: author: Lynne Cordary
body: Can you provide more details on the algorithm used in the auto-scheduler? Maybe that would help me understand better what's happening and why. I've confirmed our estimates, our team size is what it is so I can't change that, and I've checked the prioritization of the issues. Also any details on settings that could help?


author: James Godbold
body: this may help: [How does the Auto-scheduler in my plan work? \| Jira Software Cloud \| Atlassian Support](https://support.atlassian.com/jira-software-cloud/docs/how-does-the-auto-scheduler-in-advanced-roadmaps-work/)


Tags: server
Advance roadmap epic rename
Asked by sanjay:

Hi community, while i was woring with jira roadmap , i selected the issue filter to be as Epic, instead of epic the epic discription pops in the issue display field . how can i show epic it self and not epic discreption. thankyou for your input ![Capture.PNG](/t5/image/serverpage/image-id/291612i95142781AF6978F3/image-size/large?v=v2&px=999 "Capture.PNG")![adcfas.PNG](/t5/image/serverpage/image-id/291613i8E662C3956D928CB/image-size/large?v=v2&px=999 "adcfas.PNG")![sdvsd.PNG](/t5/image/serverpage/image-id/291615iDF82822D2B5C4A0C/image-size/large?v=v2&px=999 "sdvsd.PNG")


Answers:
author: Marc - Devoteam
body: HI [@sanjay](/t5/user/viewprofilepage/user-id/5364205)

Welcome to the community,

Can you clarify a bit more on all screenshots above i see APPVQST-122, with it's title.

comments: author: sanjay
body: [@Marc - Devoteam](/t5/user/viewprofilepage/user-id/3796976) As you can see in the first screen shot the name "JIRA" was suppose to be seenin the issue display field but instead "Jira Setting and Administration" appeared in the issue field (see first figure).

I would like to see my epic name directly on the roadmap page. is it possible, if so how ?

Thanks in advance


author: Marc - Devoteam
body: No this can't be done.

Advanced Roadmap shows the summary of the issue, as this is for all issues.
Customer hierarchy in Jira
Asked by Levi Clarke:

Im looking for some tips on best practices for configuring Jira. My organization runs a pretty typical SAFe situation with business goals being broken down into Epics, these Epics get broken down into quarter(ish) sized features, and then dev teams create user stories to implement these features which are executed on a sprint cadence.

I have Jira premium with Advanced Roadmaps and I'm trying to configure a customer Issue type hierarchy but I want to be able to display

1) Quarterly plans at the Epic level

2) Increment plans at the feature level

3) sprint plans at the dev team story level

Will Advanced roadmaps allow me to keep that hierarchy in place and provide visibility into the status and dependencies at all levels? I want to make sure I configure this correctly out of the gate.


Answers:
author: Hannes Obweger - JXL for Jira
body: Hi [@Levi Clarke](/t5/user/viewprofilepage/user-id/5289050)

the bottom 3 levels of the Advanced Roadmaps hierarchy are always Epic / Base issue types / sub-tasks. You can only add new hierarchy levels on top of that. What you can do though is to rename the epic type and level - but even then, the epic level will always have certain semantics, e.g. in the Backlog or Active Sprint view.

If you really want to mix additional levels into the bottom 3 levels - I wouldn't really recommend doing so - you can only do that via *issue links*. Jira itself won't recognise these issue links as parent/child relationships, but there are apps in the Atlassian Marketplace that can help with this. Happy to elaborate if this is something that might be of interest to you.

Best,

Hannes

comments: author: Levi Clarke
body: Thanks Hannes, I think the best thing for me to do is embrace the terminology and go with the tool.

Initiative -\> Epic -\> Story.

It'll take a while to get used to it but I think its the best way.


author: Wilson Sheng
body: [@Levi Clarke](/t5/user/viewprofilepage/user-id/5289050) , great question! Advanced Roadmaps is a solid choice for visualising your SAFe workflow.

And if you are looking to get more flexibility in defining your issue hierarchy, like creating additional levels like "Initiative"/ "Feature" above Epic, you can consider using [Hierarchy for Jira](https://marketplace.atlassian.com/apps/1220574/hierarchy-for-jira-custom-issue-structure-jira-tree-view?tab=overview&hosting=cloud&utm_medium=referral&utm_source=atlassian&utm_campaign=upscale_h4j_referral_web_atlassian-community_awn_prs_aho_glob_all_en__%EF%BB%BF%EF%BB%BF) in conjunction with Advanced Roadmaps.

Moreover, it will display issues at all levels on a single tree, so you can track them and visualise the dependencies easily.


author: Levi Clarke
body: In trying to configure this on my own I can't seem to move the "Epic" issue type to the top of the hierarchy. I can't "uncheck" it from the #1 level. See screen shot below:  
![Issue_type_hierarchy_-_Jira.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/290999i065F5E893F9541F3/image-size/large?v=v2&px=999 "Issue_type_hierarchy_-_Jira.jpg")


Tags: cloud