youngmon/atlassian-qna huggingface dataset:
Velocity Chart
Asked by Ganesh R:

Hello All, I am using Free Jira Standard Version. When I run and complete the sprint the velocity chart is not updated in real time. Sometimes, it shows correctly and sometime I don't see committed sprint estimate on velocity chart. Is this because it is a free version? Please advise.


Answers:
author: Vronik
body: Hello

<br />

Honestly, in the years I've been using Jira, I've never had anything like what you're talking about happen to me. Try refreshing the page in the browser, maybe the previous result is cached or try another browser. Let us know.

I also share this article with you

<https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-velocity-chart/>

comments: author: Ganesh R
body: Hi Vronika, I tried but it is not working. It is not even displaying the committed sprint estimate bar.


author: Bill Sheboy
body: Hi [@Ganesh R](/t5/user/viewprofilepage/user-id/5558790) -- Welcome to the Atlassian Community!

Please post an image of what you observe for the Velocity Chart. That may provide context to explain this symptom.

Until we see that...

One reason the "commitment" may be empty for a Sprint with Jira boards is the issues did not have an estimate value until *after the sprint started, based on its start date / time*. Is this the case for your sprint(s)?

Kind regards,  
Bill


Tags: cloud

jira-cloud
Need help in updating multi select field depending on parent issue
Asked by Ganesh Kumar Vary:

Hi,

We have a scenario where we have to update a multi select field in story level issue depending on multi select field value in it's parent epic issue.

**Field:** We have a multiselect field called ***FieldX*** both is "Epic" \& "Story" issues.

**Requirement:** If a Story is created under any Epic, it must contain the FieldX values that are there in Epic. If there are any values are added in Story other than values in Epic during it's creation, the extra value should be removed from Story.

**Eg:** if FieldX in Epic = A, B, C, D and a Story is created under that Epic with FieldX = A, B, F, H. Then F \& H must be removed from Story.

I am trying to use Jira automation to achieve this but counldn't figureout. Please help me in solving this requirement.

Thanks \& regards,

Ganesh Kumar Vary


Answers:
author: Lisa Forstberg
body: Hi [@Ganesh Kumar Vary](/t5/user/viewprofilepage/user-id/4988519) ,

How far did you get? Always good to add some screenshots of your automation to speed up the community help.

best regards

Lisa

comments: author: Ganesh Kumar Vary
body: Hi Lisa,

Thanks for the quick response. Let me try to explain the scenario clearly as I don't have any screen shots available.

______________________________________________________________________________________________

**Trigger:** Issue Created.

**Conditions:**

If type = Story AND

If Parent Exists AND

If Related Issue Condition -\> Parent Matched JQL : "FieldX" NOT IN ({{triggerIssue.FieldX}})

**Action:**-- \*I need Help here\* - (Remove only values which are not there in Parent)

______________________________________________________________________________________________

**Example:**

If: **Epic** FieldX = A, B, C AND **Story** is created with FieldX = A, B, G, H

Then: Automation should update FieldX in Story to A, B (remove only G, H as they are not there in Epic)

please let me know if you need more info.

Thanks \& regards,

Ganesh Kumar


Tags: automation

cloud

jira-cloud

multi-select
Why the same quick filter does not work in different projects?
Asked by Elena Grushetskaya:

I created in 2 projects the same components: Back-end and Front-end.

And I filled for all tasks the component fields.

Then I created quick filters with the help of JQL: component in (back-end) and component in (front-end).

In one project these two filters work in another one of the filters does not work.

What can be a problem? I checked the misspellings and sure that there are no problems with that.


Answers:
author: Nic Brough -Adaptavist-
body: Components are different items in projects, even if they have the same name. Try rebuilding the quick filter in the second one, making sure you select the components from the right project.


Tags: advanced-roadmaps
One Plan in One Program
Asked by Pepper Pancoast:

I was creating plans and programs to help road map out my projects to executives.

I ran into the issue where I could only associate a plan to one program. Why would it be limited like that? If different people managed different programs, but all cared about my singular plan, why would we limit them?


Answers:
author: somethingblue
body: Hi Pepper,

I can say that is by design per [Creating and deleting programs](https://confluence.atlassian.com/jiraportfolioserver/creating-and-deleting-programs-931037970.html):
> ***A plan can only exist in one program at a time, which means Plan A can only be added to Program 1. If you want to add Plan A to Program 2, you'll need to remove it from Program 1 first.***

Take a look at the Creating and deleting programs knowledge base article for some further ideas on how to implement plans in your environment.

In addition, please click the **feedback** link in any program page to send ideas and suggestions to the developers so they can take this functionality into consideration.

Cheers,

Branden

comments: author: Pepper Pancoast
body: Hey Branden, my main question is why you'd only want to have a plan associated to a single program! I get that it's how it currently works, but it makes me wondering if I'm not using programs \& plans correctly.


author: Roi Fine
body: Hi Pepper,

A plan is a container with multiple Jira projects.

A program is a **high level view** that groups multiple plans.

You could link some/all of your plans to a program and use the program view filters to see different sets pf plans.

Let me know if that works,

Cheers


Tags: advanced-roadmaps
Configure user weekly schedule
Asked by Adam G:

Hi,

Is there anyway to configure a users weekly work schedule besides using "exceptions" (in users)?

Example: user works:

- Tuesday: 4 hours

- Wednesday: 8 hours

- Thursday: 6 hours.

This schedule wold be for the next 6 moths so doing it manual would be crazy.

any suggestions?


Answers:
author: Walter Buggenhout
body: Hi Adam,

True. On the other hand, Portfolio is about longer term planning / capacity management / forecasting for teams, projects, even programs. In your example, your user's capacity would just be 18 hours per week. For 6 months. On a 6 month horizon, the fact that these 18 hours are being spent only on Tuesdays, Wednesdays and Thursdays becomes less important than the fact your user is capable to contribute 18 hours a week.

As such, it might be interesting to consider entering exceptions as 'reduced/increased capacity' in terms of hours available in certain weeks rather than trying to produce an exact schedule. If you configure exceptions, make sure they are indeed 'exceptions' from the usual situation.

comments: author: Adam G
body: Hi Walter,

Thanks for your reply.

My concern is making delivery dates on tasks. And that is why I feel the actual days in the week this specific dev is available is important.

That way if I use portfolio and assign a task for Monday for this dev, I should get alert that dev is not available on Monday.

If no alert would show then my client would except the task to be ready Tuesday morning which would not happen.

Anyway to address my concern?


author: Walter Buggenhout
body: Hi [@Adam G](/t5/user/viewprofilepage/user-id/1181776),

There's many different ways you can manage this. Although not explicit, I hear you say this specific user is being assigned tasks that he alone is responsible for. So assigning those tasks, setting due dates and using a dashboard for him to track those tasks and due dates will help you get a long way already.

I can imagine that you will most likely have more users on your team that you are planning / tracking work for. Sprints on a scrum board could help you focus your team(s) on a limited scope in a given time frame. Another way to track work with standard Jira functionality.

Coming to the detailed planning level where you want to fulfil the need or desire to assign work to people on specific dates, the Atlassian Marketplace has apps offering different kinds of planning features ([Planner apps on Atlassian Marketplace](https://marketplace.atlassian.com/search?query=planner)).

As an example, Tempo Planner is one that helps you schedule work for individuals on specific dates. And detailed work schedules for (groups of) people can be configured.


Tags: advanced-roadmaps

schedule
Capacity of shared team
Asked by amine benali:

Hello,

If i am using a shared team in 2 different JIRA PORTFOLIO Plans, is the capacity will be split between the two plans? or the team's capacity will be 100% in each plan ?

Please help ?

Thank you


Answers:
author: Jacques Raynauld
body: Hi

Someone knows the answer for the question ? I guess we would have to share also the individuals and the skills to have the full view but I'm not sure.

Thanks,

Jacques

comments: author: A.J. Maher
body: I came here to ask the same question. From what I can tell, it seems like only the characteristics of the team are shared (to avoid duplication of effort in creating the teams), but their capacity is not shared. Was hoping someone could confirm.


Tags: advanced-roadmaps
How to display portfolio original story points in JIRA item?
Asked by Arto Kiiskinen:

So, I have used "original story point" field in JIRA portfolio, and I would now need to see that field value on the JIRA side. How to make this field visible? I try to add the field to the JIRA screen, but it does not show up.


Answers:
author: Lineker Tomazeli
body: Any updates on this guys? I'm also interested on doing this


author: Arto Kiiskinen
body: I am using JIRA cloud, and my problem is that the Original story points field from portfolio is not visible as a locked system field in JIRA side.


Tags: advanced-roadmaps

original-estimate

story-points
Updating the Jira Portfolio custom fields via API
Asked by David Oyler:

I am building out a SAFe deployment with Portfolio based on the following hierarchy:

Portfolio Epic

Capability

Feature

I want to do a bulk upload into the various levels, but I want to automate the process to update the links without having to update 50+ features manually. After updating manually, I noted the updated custom fields 19870 and 19753 as being updated to match the parent. When I try to update the fields via API, one comes back with "not on the appropriate screen" and the other results in "internal server error".

issue.update(fields={'customfield_19870': 'GISCAP-11'})  
issue.update(fields={'customfield_19753': 'GISCAP-11'})

I know at least one of the custom fields is locked. Is there an easy API based way around this restriction? What changes need to be made in order for API based updates to be successful? The manual options is not an option based on the volume, plus the potential for human error goes up pretty quickly as the user gets bored.


Answers:
author: somethingblue
body: Hi David,  

At this time there is no official Portfolio API published. There are a few open Suggestions to Implement a REST API for JIRA Portfolio:

[JPOSERVER-438](https://jira.atlassian.com/browse/JPOSERVER-438?_ga=2.215367639.1756995434.1516634613-982752938.1513969998) - [Implement a REST API for JIRA Portfolio](https://jira.atlassian.com/browse/JPOSERVER-438)

[JPOSERVER-1814](https://jira.atlassian.com/browse/JPOSERVER-1814) - [Publish Portfolio for JIRA Java API](https://jira.atlassian.com/browse/JPOSERVER-1814)

Please vote on both of these and add your use case to the notes to add impact.

Cheers,

Branden

comments: author: David Oyler
body: Thanks. Posted a comment to JPOSERVER-438 looking a potential workaround.


author: David Oyler
body: cPrime is working on a upstream solution to the problem which will allow API access to update the Parent Link. Hopefully, something within the FY18Q4 timeframe.


author: FISICHELLA
body: Hello, do we have news from Atlassian about an official and complete API ?


Tags: advanced-roadmaps
Possible Bug : Planned capacity shown in Reports Releases
Asked by amine benali:

Hello,

I think there is a bug in the display of the planned capacity in Reports -\> Releases.

The planned capacity shown is in Days, i think it is calculated by taking all the issues linked to the release then x7 . So the results should be in HOURS not in DAYS.

Any ideas ?


Answers:
author: Thomas
body: @Hi [@amine benali](/t5/user/viewprofilepage/user-id/1180477),

The capacity report unit should match your plan estimation unit, but you need to press the "Calculate" button to update all the calculated values which would include the capacity view and report.

Let me know if that solves the issue for you or if there is more to it!

Cheers,

Thomas

comments: author: amine benali
body: [@Thomas](/t5/user/viewprofilepage/user-id/58170),

Even if you do calculate the unit of display changes but the results (numbers) are still in hours. (instead of days when you switch to days). you can test on your side.

* My week is from Monday to Friday.
* Estimate an item (in my example 10d).
* Create a team with a capacity (in my example 80 weekly/h).
* Create a release (1 sprint = 3 weeks).
* Go to Reports-\> Switch Report -\> Releases:
* The reporting of the capacity shown in DAYS should be in HOURS. (10d estimated x 7h = 70 HOURS not DAYS)


author: Thomas
body: Hi [@amine benali](/t5/user/viewprofilepage/user-id/1180477),

For some reasons I was totally looking at the capacity report, thanks for insisting.

I've created an issue here: <https://jira.atlassian.com/browse/JPOSERVER-2253> to track this bug.

Thanks for taking the time to report this, that's much appreciated.

Cheers,

Thomas


Tags: advanced-roadmaps
Can an Epic be assigned to multiple Shared Teams in Portfolio?
Asked by Kelly Schuknecht:

Our IT group is organized into 13 functional agile teams. As projects come into the queue, they are divided up into work that can be done by multiple teams based on the services or UIs that need to be updated. We would like to create one set of Epics for the project, then determine which teams have work to help complete each Epic. We are about to implement Portfolio for Jira, and would like to set up each of our functional teams as a shared team so that we can view the project work across those teams. This is working great in our testing at the story level, but we are only able to assign one Shared Team to an Epic, so it does not show up in any of the plans for the other teams.

I'm wondering if we are using Portfolio and the Shared Team concept in the way it was designed. Can you provide any insight?

Thanks!

Kelly - FirstBank


Answers:
author: Thomas
body: Hi [@Kelly Schuknecht](/t5/user/viewprofilepage/user-id/125816),

You can only manually assign one team to an issue (may it be an epic or a story) in Portfolio, the intention of manually assigning being: "Don't try to figure it out for me, this is the team that will be working on it".

I understand in your case the interesting part might be more the roll-up of teams used in the epics children, in which case I'd suggest not trying to assign manually a team a let it roll up in your plan. You might also wanna ensure the issue sources include those epics without a team on top of the filtered stories you already have.

Let me know if that helps!

Cheers,

Thomas

comments: author: Kelly Schuknecht
body: Hello Thomas!

I did not previously understand how the teams would roll up to the Epic level, but I actually just figured that out earlier today. Thank you!

Cheers

Kelly


author: Matthew Murphy
body: Kelly, do you mind sharing your findings? I am also structured in this way.

Thanks!


author: Kelly Schuknecht
body: Hi Matthew,

We assign the Shared Team at the Story level and then assign the parent Epic. If there are stories under the Epic with different teams assigned, the Epic will show in Portfolio for Jira as having multiple Shared Teams working on it.

I hope this helps!

Kelly


author: miquel
body: Thanks Kelly! It helped us as well :)


Tags: advanced-roadmaps
Portfolio Capacity is mixing up sprints
Asked by FlipThisHouse2:

based on the following:

* Using one project in Jira
* Using multiple scrum boards, one per team (based on a filter)
* Each SCRUM board has its own sprints
* Each SCRUM team is using its own board

We notice that when looking into the capacity view per team, sometimes sprints from Team B will show under Team A.

I was expecting to only see the sprints that by board per team, but instead it looks like the capacity view is ignoring the data source and grabbing whatever sprints are under the project (not doing it by board, but rather by project).

Is this behavior by design? or is this a bug?


Answers:
author: Ruchi Tandon
body: Hey Mike, not sure you have seen this blog already [5 ways to become a planning master with Portfolio for Jira](https://www.atlassian.com/blog/jira-software/5-ways-to-become-a-planning-master-with-portfolio-for-jira)

Especially, this part :

"1. Blend product roadmaps into sprint planning"

Does that help to do capacity planning per board?

If not, perhaps it might help to add some screenshots to show exactly what you have on your side.


Tags: advanced-roadmaps
In portfolio I have a release showing as "overbooked" while i still have capacity available
Asked by Mathieu Lapre:

I am using portfolio with a kanban team. The team contains 9 members with 40 hrs per week capacity. I have 6 stories. 5 of them are assigned to 5 members of the team (one per person). Portfolio therefore predicts each story will take a month to perform based on one assignee doing a story. The capacity shows that for each week, I have 4 member of free capacity left. My 6th story is not assigned to anyone. This 6th story is assigned to a different release but this release as the same start date as the other release to which the other 5 stories are tagged.

In the portfolio setting, I have set the option that up to 12 people can work on a single story. Therefore, I would expect that this 6th story that is unassigned would use up the capacity available each week and start in parallel with the 5 others. Instead, portfolio forces it to start only once the other 5 assigned stories are done. When I look at the capacity, it is ridiculous because I see that my team is occupied at 50% during the time the team works on the 5 assigned task. HOw can I force parallelization of the tasks.

thanks

Mathieu


Answers:
author: Cindy
body: Do you have any dependencies?


Tags: advanced-roadmaps
Portfolio User Story and Configuration Issues
Asked by Thomas B:

Hello all,

I am new to JIRA Portfolio and I watch a few YouTube videos regarding the software. It seems like my JIRA Portfolio is not accurately estimating time frames. It is trying to place all of my Releases in the same Release Date which makes no sense. Also - if I add User Stories to an Epic that is tied to a Release, JIRA Portfolio is not recognizing the new stories. Is there any one-on-one training or more meaningful video I can use to help setup my JIRA Portfolio?

Please help. Thanks!


Answers:
author: Thomas
body: Hi [@Thomas B](/t5/user/viewprofilepage/user-id/744438),

I'd suggest having a look at our on-demand Portfolio Webinar: <https://www.atlassian.com/webinars/software/get-started-with-portfolio-for-jira>

The Atlassian University also offers courses for Portfolio for Jira:

<https://training.atlassian.com/instructor-led-training/planning-with-portfolio-for-jira-public-virtual>

I hope that will help you get started! Don't hesitate to give us feedback on those content and the [documentation](https://support.atlassian.com/portfolioforjira/).

Cheers,

Thomas

comments: author: Thomas B
body: The dynamic release was not working because some issues related to the future release were already in progress. After watching the YouTube video again, I noticed the only difference was the 'Initiatives' level that was created.

All in all, I was trying to control the release dates and times instead of letting JIRA dynamically set those times.

Thanks for the help!


Tags: advanced-roadmaps
Portfolio User Story and Configuration Issues
Asked by Thomas B:

Hello all,

I am new to JIRA Portfolio and I watch a few YouTube videos regarding the software. It seems like my JIRA Portfolio is not accurately estimating time frames. It is trying to place all of my Releases in the same Release Date which makes no sense. Also - if I add User Stories to an Epic that is tied to a Release, JIRA Portfolio is not recognizing the new stories. Is there any one-on-one training or more meaningful video I can use to help setup my JIRA Portfolio?

Please help. Thanks!


Answers:
author: somethingblue
body: Hi Thomas,

I'm sorry to hear that you're running into these issues.

* Are all your releases in the [same project](https://confluence.atlassian.com/jiraportfoliocloud/creating-and-configuring-cross-project-releases-828785313.html)?

In addition there are [some resources](https://www.atlassian.com/partners) that can assist with training, etc. Hopefully this helps.

Cheers,

Branden


Tags: advanced-roadmaps
Jira Portfolio - how do I commit changes to Jira?
Asked by Jason Coan:

I made a test project with epics, tasks, versions, and sprints.

I created a Plan in Portfolio. Clicked calculate, it puts tasks into sprints based on peoples availability. Now how do I get those changes committed to Jira so that the tasks are moved into the sprints as shows in Portfolio?


Answers:
author: Danny Zuccaro
body: Hi Jason,

Here is a [walk through](https://confluence.atlassian.com/jiraportfoliocloud/committing-your-plan-changes-828785217.html) on committing your plan changes in Portfolio.

Hope this helps,

Danny

comments: author: Jason Coan
body: Read that, did that, all issues remain in backlog, all sprints remain empty.


Tags: advanced-roadmaps
Is Portfolio available in cloud?
Asked by Darren Martin:

We are looking to implement an Agile support tool and Jira Cloud is considered for a trial. While we will initially be trialing on individual projects we would ultimately be wanting to apply a level of Portfolio management within the tool across our full project portfolio.

I've heard Portfolio for Jira isn't available for Cloud but can't find any definitive info on this.

Any insights on this subject?

Regards

Darren


Answers:
author: Thomas
body: Hi [@Darren Martin](/t5/user/viewprofilepage/user-id/1179834),

Portfolio for Jira Cloud does exist as a product! [Here is the documentation](https://confluence.atlassian.com/jiraportfoliocloud/portfolio-for-jira-home-715263250.html).

what you may have heard is that the feature set might be slightly different due to our [different priorities](https://www.atlassian.com/blog/announcements/prioritizing-roadmaps-cloud-server-data-center).

Cheers,

Thomas

comments: author: Bill Schenck
body: [@Thomas](/t5/user/viewprofilepage/user-id/58170), I was asked if we have the newest version of Portfolio in our Cloud instance. Do I have to do anything to ensure it is the latest version, or is Portfolio updated automatically in Cloud?

Thanks.

Bill


author: Thomas
body: Hi [@Bill Schenck](/t5/user/viewprofilepage/user-id/639949),

Portfolio is updated automatically in our Cloud offering, and no action would be required on your side to have it happen.

Cheers,

Thomas


author: Bill Schenck
body: Great, thanks!


Tags: advanced-roadmaps