youngmon/atlassian-qna huggingface dataset:
What's the difference between Committed Story Points and Planned Story Points?
Asked by Emma Willcox:

In Jira Align, I can see Committed and Accepted Story Points on the M1 Report and Planned and Accepted on the Teams View (Team \> Manage Teams \> Select Team \> Sprints).

The Committed and Planned Story Points for my teams in Jira Align are almost always different.

What's the difference between Committed and Planned Story Points please? When is each value determined?


Answers:
author: Allan Maxwell
body: Points Committed only counts the LOE/Story Points on those Stories that were assigned to the Sprint before the Sprint Start Date. Points Accepted includes the LOE of all Stories accepted regardless of if they were assigned to the Sprint before the start date or after.

comments: author: Jennelle Stearns
body: In addition to what [@Allan Maxwell](/t5/user/viewprofilepage/user-id/3502714) already defined above, planned story points are typically the stories assigned in the sprint currently. However, I always recommend selecting help on the specific report/page you are reviewing to see how the field and calculations are defined and calculated.


author: Emma Willcox
body: Thanks both - this has been bugging me for ages! Great to get a really clear, specific answer.


author: Stephanie Davis
body: How does the integration with Jira Software play into this. Is it the anchor sprint start date that's used for committed or the sprint start date coming from Jira Software through the sync?


Tags: cloud
How can we calculate " Project Completion Percentage " ( EVM or any other technique ) using Jira ?
Asked by Dushantha_106202:

We have a lot of agile projects running on scrum with 2 weeks sprints , any idea on how to calculate the project completion percentage directly or indirectly using information available on Jira ?


Answers:
author: Iryna Komarnitska_SaaSJet_
body: Hi [@Dushantha_106202](/t5/user/viewprofilepage/user-id/5223057)

I assume you will find the [Cost Tracker for Jira Cloud app](https://marketplace.atlassian.com/apps/1229405/cost-tracker-for-jira-cloud?tab=overview&utm_source=Atlassian_Community&utm_medium=refferal&utm_campaign=Comment_How-can-we-calculate_08062023) useful. My team developed it.

Don't let the name scare you. The add-on is functional and can meet your needs.

It has cost reports, time reports, and much more. With the planned budget and planned time features, you can also view the approximate progress of a sprint or project.

In the articles below, we've written a little bit about the features of the app:

* [Managing Sprint Costs in Jira with Cost Tracker](https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Managing-Sprint-Costs-in-Jira-with-Cost-Tracker/ba-p/2276635#M5967)
* [EVM: The easiest way to get accurate data from Jira](https://community.atlassian.com/t5/Marketplace-Apps-Integrations/EVM-The-easiest-way-to-get-accurate-data-from-Jira/ba-p/2313404#M6252)

I hope you find them helpful!


author: Christoph Piotrowski _catworkx_
body: Hello [@Dushantha_106202](/t5/user/viewprofilepage/user-id/5223057) , this question is not related to Jira Align so you might ask this also in another group to get some answers.

However, the question is also not that easy to answer at least for me without more information. I know EVM from classical projects that have a fixed scope. Question is, if your agile teams work on such a fixed scope. Or simpler: how do you define the "end" of the project? Based on this you could define these "agile EVM metrics".

PMI has an article that might help from theory perspective: [Earned Value Management (EVM) - Understand Agile Project Progress (pmi.org)](https://www.pmi.org/learning/library/earned-value-management-understand-agile-6567)

Looking to the metrics used in that article, I don't think that Jira standard provides hat reporting.

What you should have a look at are the reports in Jira, especially the version/release report: [View and understand the version report \| Jira Software Cloud \| Atlassian Support](https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-version-report/)

Also have a look to the release burndown report. This predicts the time needed to finish a release based on current velocity: [View and understand the release burndown report \| Jira Software Cloud \| Atlassian Support](https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-release-burndown-report/)
Prioritizing Feature on Product Line Board
Asked by Nuruddin Topan:

I want to see Features on Product Line Board prioritized based on WSJF score. How can I do so?

When I open PLB Dashboard I see all features but I am unable to see how these features are prioritized? What is been considered for features to get them listed in order?

I can sort features based on WSJF value on Feature backlog. Can I sort features on PLB board based on WSJF value?


Answers:
author: Nuruddin Topan
body: Thanks Allan for quick answer.

Yes. Its Program board.

It will be helpful if Features on this board can be prioritized.

Awaiting bug to be fixed.

Thanks.


author: Allan Maxwell
body: It looks like you guys are have changed the names of some of pages in Jira Align, so I'm including a screenshot just to be sure that we are talking about the same thing.

The Product Line Board does not currently sort by priority. I believe there is an existing bug for this, but it does not hurt to complete a support request.

![Screenshot 2023-05-18 at 3.20.03 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/258154i51828671486FD3A1/image-size/large?v=v2&px=999 "Screenshot 2023-05-18 at 3.20.03 PM.png")
Why are Process Flows limited to one entity?
Asked by Stephanie Davis:

We created a Process Flow for Intake for Epics. Then we tried to create another Process Flow for Product Marketing for Epics, but it seems that you can only have a single Process Flow per entity type.


Answers:
author: Jennelle Stearns
body: [@Stephanie Davis](/t5/user/viewprofilepage/user-id/5152002) You can have more than one process flow for a work item type (e,g, Features, Epics). However, a Program (ART) can only be associated with one process flow per work item type. For example, looking at the picture I have attached, the Mobile Program can only be associated to either the "Personal Banking Solution Jira Epics" process flow or the "Another Feature (Jira Epic Process Flow)" for the Feature Work Item Type but it can't be associated to both.

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

comments: author: Stephanie Davis
body: Thanks for clarifying. It still creates a limitation for us as we try to manage to a standard process across all of our Programs.


author: Rich Sparks
body: I may be misunderstanding, but if you want to have a "standard process across all" of your programs, this will work fine. You can create a process flow then assign it to many different programs. Then each program will use the same flow.

In [@Jennelle Stearns](/t5/user/viewprofilepage/user-id/3697699) message above, she says each Program (ART) can have just one flow for each work item type. But that flow can be shared by many different programs.


author: Stephanie Davis
body: Right but I'm talking about two different processes that cross all the same Programs.
An entity can only be pulled into one custom Kanban Board
Asked by Stephanie Davis:

I discovered custom Kanban boards and found it to be a really nice feature for customizing a card view of Epics until I realized that you can only pull an Epic into a single Kanban. Why does this limitation exist? It shouldn't matter how many custom Kanbans I want to pull the same Epic into. I might have a Marketing custom Kanban and then one for Product Management which might both have the same Epic.


Answers:
author: Christoph Piotrowski _catworkx_
body: Hello [@Stephanie Davis](/t5/user/viewprofilepage/user-id/5152002) , yes, the cards can be pulled into one board only. I think the reason behind this is, that double work should be avoided. If you see a Kanban boards as a tool a team is actively working with, the limitation makes sense. If you want to use Kanban boards to visualize upcoming items for certain (multiple) teams, your requested feature would be a nice improvement.

However, we (catworkx) currently do not miss this feature as our customers have Jira linked to Jira Align. For Features/Stories these views can be achieved easily with Jira Kanban boards. For the portfolio level this is not possible as the Epics remain in Jira Align.

Maybe this is a workaround for your use case: if you want to have a view on portfolio epics that are relevant for a certain team only, you can work with tags. Tag the epics interesting for your marketing team and apply a tag filter in the Kanban board room.

If that's not helpful for your case, you can request this feature at the ideation portal for Jira Align here: <https://internal.jiraalign.com/ideaZone>
Is there a report that shows the estimated story points and actual LOE?
Asked by Rebecca Hylek:

In an effort to help our business leaders have a better understanding of the work effort to complete features, we would like to look at our T-shirt estimation conversions compared to the actual level of effort for planned work. Our goal is to see if there are any trends in our historical data to support a revision of our T-shirt estimation conversion chart.

Is there a report in Jira Align that will show both? For example, with the feature below, the T-shirt size should have been Medium because the LOE was more than double the work effort and it took more time and resources than expected.

Feature:

FORD-1234

T-shirt size X-Small

* Estimation Conversion
  * 12 Member Weeks
  * 2 Team Weeks
  * 3 FTE/mo
  * 18 Story Points

Actual Story Points (LOE) to complete the feature = 38


Answers:
author: Jennelle Stearns
body: [@Rebecca Hylek](/t5/user/viewprofilepage/user-id/4797610) You could go to the features grid in Jira Align (Program-Features), and then add the columns T-Shirt, Points (This is the Feature points using the conversion table to convert your t-shirt size to points), and Story Points (this is the sum of the LOE's from the stories).

![Snag_2ac2307c.png](https://community.atlassian.com/t5/image/serverpage/image-id/257608iB89677B4C643808C/image-size/large?v=v2&px=999 "Snag_2ac2307c.png")
Will disabling an ideation group cause us to lose submitted ideas?
Asked by Donald Prather:

We have completed an idea gathering campaign using Jira Align's Ideation module and we want to close the campaign to further submissions. We still need to triage and work through all of the submitted ideas and will eventually turn some of these into work tasks. I see that we can disable an ideation group, but I just want to be sure that doing so will not result in us losing the ideas collected in that group. Thanks in advance!


Answers:
author: Allan Maxwell
body: The Ideas in a disabled Groups will not be deleted. If you re-enable the Group, the Ideas will be intact. The challenge is viewing Ideas from disabled Groups. You cannot view them in the Idea backlog or on the main Ideation list view. You CAN access through the API however. {{base_JA_url}}/Ideas?$filter=groupId eq 9
If our team moves to cloud, can we get rid of any resource mngmt add-on?
Asked by Jason Chayer:

I have TeamBoard ProScheduler, if we move to cloud, can we get rid of this add-on? Will Advanced Roadmaps accomplish the same thing? Can you plan out tasks in Advanced Roadmaps?


Answers:
author: Teresa
body: Hi [@Jason Chayer](/t5/user/viewprofilepage/user-id/4966970)

I'm Teresa from DevSamurai, the creators of the TeamBoard ProScheduler app.

Our app supports **Cloud, Server, and Data Center**, and it offers a variety of features that surpass those found in Advanced Roadmap. These include a TimeLine, Gantt Chart (with baseline, dependencies, critical path, milestones, etc.), and numerous other features that we believe you'll find beneficial.

<br />

Should you have any questions or require additional information, feel free to reach out to our [support desk](https://devsamurai.atlassian.net/servicedesk/customer/portal/6/group/10/create/47) or send us an email at: atlassian@devsamurai.com to schedule a demo.

Thank you.

comments: author: Jason Chayer
body: [@Teresa](/t5/user/viewprofilepage/user-id/5112919) - thanks for reaching back out. We currently use TeamBoard ProScheduler.


Tags: advanced-roadmaps

jira-cloud

jira-software
Ranking of Epics in one plan affects ranking of Epics in others
Asked by JA:

Hello,

We have one main plan our leadership team uses to prioritize Epics that come in as part of our project intake process. We have various other plans also based on team or squad where project leads are also prioritizing the same Epics, within their team/squad. What's happening is that when teams/squads are prioritizing their Epics, it changes the rank of Epics in the larger main plan. This is problematic because leadership has them prioritized the way they want, and then things get rearranged by the time they view the plan the following week.

Is there a way to avoid this from happening? It would be nice if we could lock the prioritization in place for a specific plan or something but not seeing anything out there on this.

Thanks in advance for any help!

Justine


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

That observation is correct. The reason behind this, is that your Epics are unique issues in Jira. While you may have your epics appear in multiple plans, updating their ranking impacts the one unique ranking they have in Jira, behind the scenes. And so yes, reranking them in one plan does affect other plans. That cannot be avoided.

Organisations working at a certain scale sometimes use a ranking system that is not depending on the issue ranking of a tool like Jira, like WSJF (Weightest Shortest Job First). Basically, they apply a ranking system of their own, adding it to a custom field in Jira and allowing that to be used for sorting instead.

Hope this helps!


Tags: advanced-roadmaps

server
How to add a jira project to an existing cluster of projects managed in advanced roadmaps?
Asked by Stefan De Troch:

We have a cluster of jira projects managed with advanced roadmaps. We now would like to add another project to this cluster.

That seems possible, but how can I use the sprints from the cluster for the issues in that additional project.

Any hints how to get this working?


Answers:
author: Stefan De Troch
body: Hi Eddy,

I created a cluster of projects, 2 normal projects with epics, stories and tasks; plus a project with initiatives and super-initiatives. those have a common board, where we have defined a number of sprints. This works nicely.

I now added another project to that first common board. But if I want to assign issues from that new project to one of the sprints in the common board, I cannot do this.

My question is whether that new projects, or at least it issues, could use those earlier defined sprints.

Kind regards,

Stefan

comments: author: Eddie Meardon
body: [@Stefan De Troch](/t5/user/viewprofilepage/user-id/5237885)

This sounds like something that might need to be escalated to our customer service. Reach out to them at support.atlassian.com/contact. They're usually pretty quick to respond and also very nice :)

Sorry I can't be more help

Eddie


author: Eddie Meardon
body: Hi [@Stefan De Troch](/t5/user/viewprofilepage/user-id/5237885),

It sounds like you want to assign issues to a different sprint. To do this, make sure that the **Sprint** field is showing on your timeline, then select the sprint you'd like to assign it to.

One quick thing, though: if you're trying to use capacity planning, you'll need to use **Boards** as the issue source (not projects or filters). That done, you should then see the sprints on your timeline when issues are grouped by **Team** or **Sprint,** and you can easily reassign the issues to a sprint you desire.

Does this help?

Cheers

Eddie


Tags: advanced-roadmaps

server
Grouping Cross project Releases in the Roadmap view
Asked by Marc-Andre Dufort:

Hello!

Is there a way to group cross-project releases in the Roadmap view? In the view setting, I chose Group by Release, but I still see 2 releases. Any idea what I could be doing wrong? I'm still learning how to use Advanced Roadmaps.

Thanks![CrossProjectRelease.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/261381i4C6B4949124B5BBF/image-size/large?v=v2&px=999 "CrossProjectRelease.jpg")


Answers:
author: Eddie Meardon
body: Hi [@Marc-Andre Dufort](/t5/user/viewprofilepage/user-id/2798407)

So bad news is that there isn't a way to do this. Cross-project releases are only a feature in Advanced Roadmaps, and it's an attribute applied to the releases, not the issues.

That said, you can always file a feature request ticket on [our public suggestion tracker.](https://jira.atlassian.com/secure/Dashboard.jspa?selectPageId=10440)

Cheers

Eddie

comments: author: Marc-Andre Dufort
body: Thanks [@Eddie Meardon](/t5/user/viewprofilepage/user-id/3938537) , this is really sad news. With really low expectations, I will make a request.


Tags: advanced-roadmaps
Labelling and Reflecting status on bars (schedule)
Asked by Mahesh Kumar CD:

Hello,

Have query on the Advance roadmaps:

1. Can the advance roadmaps display epic / story / task names in the schedule bars?

2. Also, can the schedule bars depict status similar to the showing status in the Fields column using Progress (count)?

Thanks

Mahesh


Answers:
author: Walter Buggenhout
body: Hi [@Mahesh Kumar CD](/t5/user/viewprofilepage/user-id/5047970),

To both questions, the answer is - unfortunately - **no**. The schedule's bars can be coloured based on:

* *component*
* *issue type*
* *label*
* *priority*
* *project*
* *status*
* *team*
* *supported* custom*fields you add*

But apart from the colouring options, there is not much you can do. The closest you can come to achieve what you seem to be trying to do, is creating a view that has just 2 columns you mention in the scope view and leave enough room for them to display side by side with the schedule. That could look somewhat like this:

![Screenshot 2023-05-29 at 18.03.54.png](https://community.atlassian.com/t5/image/serverpage/image-id/260049i6B86B1859B862150/image-size/large?v=v2&px=999 "Screenshot 2023-05-29 at 18.03.54.png")

Having the information displayed side by side with the schedule may even leave less room for interpretation for the user than having it inside the bars.

Hope this helps!

comments: author: Mahesh Kumar CD
body: Thank you [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225) .


Tags: advanced-roadmaps

cloud
Add other relevant dates for the release to track in the timeline section
Asked by Geraldine:

Other than Start and Release date, can we add other relevant dates in the details of our Release and also be able to track this in the timeline section?


Answers:
author: Bree Davies
body: Hey Geraldine - not today I'm sorry. But I would love to hear more info on the sorts of other dates / details you'd like to track here?

Thanks!

Bree \| Advanced Roadmaps PM.

comments: author: Geraldine
body: Code lock date would be great!


author: Bree Davies
body: [@geraldine](/t5/user/viewprofilepage/user-id/4980139) is that usually a single date or a date range?


author: Geraldine
body: Single date


Tags: advanced-roadmaps
Advanced Roadmap Grouped by Release does not show Rolled-Up dates for Release
Asked by Aimee Quinn:

Using the data center version of Advanced Roadmaps, how do we get a roadmap grouped by Releases to show roll up dates for all items below? We have roll up dates checked but it does not show the dates on the release line.


Answers:
author: Crystelle S
body: have you looked at the Cross Project Release that you can create? I assume you are looking across releases.


Tags: advanced-roadmaps
Issues and Roadmap
Asked by ANTONIO GOMEZ ASENCIO:

Hello, I'm trying to create a report in POWER BI based on the data we have in JIRA regarding the advance roadmaps and corresponding issues. What alternatives do I have to create a report that updates automatically? I have tried using the JIRA database, but there is no relationship between the roadmap tables and the issues.

Thank you for your assistance.


Answers:
author: Liubov Topchyi
body: Hello [@ANTONIO GOMEZ ASENCIO](/t5/user/viewprofilepage/user-id/5210488) ,

If you use Jira Data Center, you may try to build dashboards in Power BI and schedule automatic refreshes in Power BI Service. So the visualization and auto-updates can be done with the help of Power BI tools.

To export the data from Jira Data Center into the Power BI Desktop for further analytics, you can try [Power BI Connector for Jira](https://marketplace.atlassian.com/apps/1221150/power-bi-connector-for-jira?hosting=datacenter&tab=overview).

It supports the export of the Roadmap tables. Please find the details in the documentation: <https://aserve.atlassian.net/wiki/spaces/POWERBI/pages/1563262991/Advanced+Roadmaps+formerly+Portfolio>

The [Power BI Connector for Jira](https://marketplace.atlassian.com/apps/1221150/power-bi-connector-for-jira?hosting=datacenter&tab=overview) is available for a trial. We'll be happy to help you during the trial if you have any questions. Please feel free to contact our [Help Desk](https://aserve.atlassian.net/servicedesk/customer/portal/16).

Regards,

Luba


Tags: advanced-roadmaps
Why am I unable to create issues in Jira Plans
Asked by Justin Jose:

When creating an issue in Advanced RoadMaps I encounter an error requiring a description even when the description field has been entered.

![Description Error.PNG](/t5/image/serverpage/image-id/259003iBBF0C8C57656D2DD/image-size/large?v=v2&px=999 "Description Error.PNG")


Answers:
author: Bree Davies
body: Hey Justin - I'm sorry to see this! Is it still happening? Can you please let me know if you're on Cloud / DC / Server? I'd recommend raising a support ticket: [support.atlassian.com](https://support.atlassian.com/)

Thanks  
Bree

comments: author: Justin Jose
body: we are using Jira Data Center


Tags: advanced-roadmaps
Using Advanced Roadmaps to automatically schedule start and end dates based on estimated hours
Asked by Chloe P:

Hi,

I'm new to using Jira Advanced Roadmaps and I've looked through documentation however I haven't found the answer I'm looking for and hoping someone may be able to help me.

I have a plan that will be open to everyone and I want users to be able to create tasks but not fill in a start or due date field, rather an estimated hours for how long it will take to complete and have Jira automatically schedule the dates so that the start date is immediately after the previous task and the end date is based on the estimated hours to complete taking into account the teams weekly capacity. This means each task someone creates is automatically scheduled one after the other.

I know the scheduling assistant can help with certain parts of this but from what I've read it still seems to be based on dates that you input yourself rather than Jira figuring that out for you.

Hope that makes sense!

Any help is greatly appreciated.

Thanks,

Chloe


Answers:
author: James Godbold
body: I've just started playing with this plugin as I have the same issue. From what I can see there is no option to put effort against an issue.

I'm certain the old version of Jira roadmaps had this functionality, bit of a shame to see it's been removed.

[https://marketplace.atlassian.com/apps/1220860/activity-timeline-resource-planning-time-tracking?tab=overview\&hosting=cloud](https://marketplace.atlassian.com/apps/1220860/activity-timeline-resource-planning-time-tracking?tab=overview&hosting=cloud)


Tags: advanced-roadmaps

server