youngmon/atlassian-qna huggingface dataset:
JIRA Portfolio capacity report shows wrong number of storypoints
Asked by Arto Kiiskinen:

I have a sprint called "Sprint 40"

this sprint has seven items in it, 6 stories and one task.

the combined storypoints for these seven items is 44.

When I go to the JIRA portfolio main page, it shows the seven items in the sprint 40 ok.

When I review and calculate the storypoint values in the list below, the storypoints for the seven items in the sprint 40 are showing up correctly.

My problem is this: when I go to JIRA Portfolio reports section, and click on the sprint 40, it says there are 41 storypoints in the sprint.

I tested by changing the values of different stories and tasks, and after clicking "Calculate" and returning to the report, all the changes seem to reflect correctly in the value. But why is it 41 and not 44? It is very irritating and degrades the trustworthyness of the report when it is incorrect.


Answers:
author: Earl McCutcheon
body: Hello Arto,

It sounds like an issue with 3 story points associated to it is already completed at the time of calculation, and therefore not included in the current capacity of the team. The capacity report does not take into account completed or historic issues [as covered in this feature request](https://jira.atlassian.com/browse/JPOSERVER-1267).

Can you add the Status of the issues in the sprint to see if this is the case.


Tags: advanced-roadmaps

jira-software
Potfolio Epics don't have an Epic ID
Asked by Linda K.:

Creating an epic under the portfolio plan doesn't populate an Epic ID number.

For example, if I create an epic in Jira Software, it assigns the ID as "EPIC_23" but if I create the epic under the portfolio plan it assigns the ID "EPIC" and doesn't add that to my Jira software issues list.


Answers:
author: Dave
body: Hi Linda,

When you create an Epic in Portfolio, did you do a commit changes? Portfolio will only persist changes or ticket creation once you commit the changes back to Jira.

There should be an **uncommited changes** lozenge by your plan name, you can click on this and it will show you the changes or issues you created in Portfolio, clicking on **commit**will then put it through to Jira Software and after this it will reflect back on Portfolio the issue key assigned to it.

Hope this helps.


Tags: advanced-roadmaps
Unresolved issue in Portfolio
Asked by Dania Zaccara:

Hi all,

I've a problem with Portfolio. I notice that there were some user story not imported in my portfolio plan. The only difference I found was the resolution field, filled out as Unresolved on the user stories I can't see in Portfolio.

Why this?

Thanks


Answers:
author: Earl McCutcheon
body: Hello Dania,

My associate Martin put together a list of items that Could cause issues to not show up in a plan, as a fist step I would recommend checking this thread out:

- <https://community.atlassian.com/t5/Jira-questions/Issues-not-showing-up-in-Portfolio-Live-Plans/qaq-p/108507>

But as you also noted that the Resolution field showing as Unresolved on issues that are not showing up, I would recommend starting at the filter used by the board tied to the plan, as this would indicate that there is something in the filter that is excluding issues where the resolution is empty.

Next I would recommend checking if there is a workflow conflict causing open issues to show as resolved as described here:

- <https://confluence.atlassian.com/jirakb/closed-issues-show-as-unresolved-or-open-issues-appear-as-resolved-with-strike-through-151126301.html>


Tags: advanced-roadmaps

resolution
trial mode and can't schedule releases to include in my portfolio plan
Asked by Linda K.:

I have Jira Software and Portfolio as a trial and have configured my epics, tasks, etc. I am unable to find anywhere to create releases though. Apparently these are needed in order to visualize my plan against the timeline.


Answers:
author: Earl McCutcheon
body: Hello Linda,

Details on setting up Releases in Jira Portfolio can be found here:

* [Releases](https://confluence.atlassian.com/jiraportfolioserver/releases-802170559.html)

The page includes a demo video with the steps and example on the process.

Alternatively the Versions can be created on the jira side and will be included into the plan, details on creating a Version for a release can be found here:

* [Managing versions](https://confluence.atlassian.com/adminjiraserver/managing-versions-938847201.html)

-Earl


Tags: advanced-roadmaps
use one issue type in multi hierarchy level in portfolio for jira
Asked by Mohammad Amin Sheikhzadegan:

Hi

can I set one issue type in multi hierarchy level in portfolio for jira ?!

for example in our case, issue1 (with issue type A) is parent of issue2 (with issue type B) and then I wan to create issue3 (with issue type A) as child of issue2.

this is what I want :

issue1 (with issue type A) ----\> issue2 (with issue type B) ----\> issue3 (with issue type A)

Thanks


Answers:
author: Earl McCutcheon
body: Hello,

Once you map a Hierarchy level to an issue type, the issue type cannot be linked to another Hierarchy level, its a one to one mapping relationship for a unique identifier.

The Scenario you presented would have "Issue 3" as a child of its own issue type, and create a circular referance and no longer be in a Hierarchal layout.

For more information on the setup and configuration options, please refer to:

- [Configuring initiatives and other hierarchy levels](https://confluence.atlassian.com/jiraportfolioserver/configuring-initiatives-and-other-hierarchy-levels-802170489.html)


Tags: advanced-roadmaps
JIRA portfolio - stories are taken in concurrent
Asked by Mohamed Ali:

After creating the plan, different stories and epics taken concurrently. I want that to be changed in a way once story A is complete Story b can be taken.

Example:

Story A (100 story points) and Story B (100 story points)

Team velocity: 100

portfolio schedule showed like : Sprint 1 - Story A and B (each 50 points burned)

Sprint 2: both stories are done.

Expected: Sprint 1: Story A complete and Sprint 2: Story B complete

Can you please help on how to change the settings to incorporate this?


Answers:
author: Earl McCutcheon
body: Hello Mohamed,

It sounds like Story B has been manually added to the same sprint that Story A is part of. And when Manual association is in place this overrides the calculation performed by portfolio.

Check out the [Scheduling Behavior](https://confluence.atlassian.com/jiraportfolioserver/scheduling-behavior-802170552.html) Documentation for more details on this.

-Earl


Tags: advanced-roadmaps
JIRA PORTFOLIO - Max Plans per Program
Asked by Michael Schaaff:

I'm doing research into the limits of portfolio and found a page explaining the ability to set limits on how many tickets are displayed in your plan. This lead me to question

What is the maximum number of plans a program can hold?

I couldn't find anything online talking about this so figured I'd ask.


Answers:
author: samrobertsofficial
body: Hi [@Michael Schaaff](/t5/user/viewprofilepage/user-id/1182120),

There is no practical limit of how many plans you can have in a program. However as a guideline:

* If the sum total of the issues in all the program is \> \~5000 performance issues will start to occur

On our side we see the most benefit from programs when they consume about 3-5 plans, but this is the average case. How many plans were you thinking of using? Do your plans represent a particular team, product?

Thanks,

Sam

comments: author: Michael Schaaff
body: So we have about 4 levels of management (oy)....and they all want to be able to see the progress of their products. So I am starting to set up a Plan for each mid-level manager, but then there's the Program for the next level. So I was going to make a Program for the each tier and just include all the plans from the programs below it....

To illustrate:

Program 1:

1. Plan A
   1. JIRA queue 1
   2. JIRA queue 2
2. Plan B
   1. JIRA queue 3
   2. JIRA queue 4

Program 2:

1. Plan C
   1. JIRA queue 5
   2. JIRA queue 6

<br />

Program for the manager who manages the managers of 1 and 2:

1. Plan D (covering Program 1 \& 2 from above)
   1. JIRA queue 1
   2. JIRA queue 2
   3. JIRA queue 3
   4. JIRA queue 4
   5. JIRA queue 5
   6. JIRA queue 6
2. Plan E (covers some other subset of programs)
3. Plan F

and then just build up for each level of management. Which could potentially put a LOT of tickets into a program. This is the only way I could think to accomplish what they're asking.


author: samrobertsofficial
body: That sounds like it should work to me Michael! Let us know if you run into any performance issues in the future by lodging a support issue: <https://support.atlassian.com/contact/#/> so that we can investigate further.

Also, we'd love it if you could give us feedback about programs after you use it through the "give feedback" button which you can find in the top right when viewing a program.


Tags: advanced-roadmaps
Can i define the hierarchy under epic
Asked by sudheer:

Can i define the hierarchy under epic?

Currently i can manage Business Requirement-\>Epic-\>Feature/Story-\>Sub-task But i need the hierarchy like Business Requirement-\>Epic-\>Feature-\>Story-\>Task/Sub-Task


Answers:
author: Tarun Sapra
body: Hello [@sudheer](/t5/user/viewprofilepage/user-id/1251309)

You can have the hierarchy you want, using the "Issue linking" feature. From your hierarchy it seems that you are trying to implement the "SAFe" framework in JIRA which is fine as well but I personally recommend to stick to "Epic\<-\>Story" hierarchy in JIRA because it's so tightly coupled in JIRA.

So when you move the Epic an level up and have the hierarchy Epic -\> Feature -\> Story then you loose the Epic\<-\>Story coupling which will lead to confusion once you start using the system at a larger scale. Because you have fields like Epic Name, Epic Link and on boards it's Epic Panel and in plugins like SR there are JQL functions like "issuesInEpic" etc

So there is a tradeoff when going forward with this approach. My preferred hierarchy is

"Initiative -\> Epic -\> Story -\> Sub-Task" , it works well with JIRA and with plugins.

comments: author: sudheer
body: [@Tarun Sapra](/t5/user/viewprofilepage/user-id/781576) Thanks for the information but my client requesting the above flow.


author: Nic Brough -Adaptavist-
body: No, Jira does not have sub-tasks of sub-tasks.

comments: author: sudheer
body: My qsn is under Epic i want to create Feature and under Feature i want to create Story and for that story i want to create Task. Is it possible?


author: Nic Brough -Adaptavist-
body: Yes.

Assuming you have a default Jira, you already have an issue type called task, and it's a parent level one. You will need to rename that to something else, then you will be able to create "task" as a sub-task type and use it beneath Stories.


author: sudheer
body: *[@Nic Brough -Adaptavist-](/t5/user/viewprofilepage/user-id/781454) But how can i remove the Task from parent group, Could you please help me on this.*


author: Nic Brough -Adaptavist-
body: You rename it to something else. Or delete it (and tell Jira what other types to swap the existing tasks to)


author: Suhas P
body: You can have a look at Structure for JIRA

<https://marketplace.atlassian.com/plugins/com.almworks.jira.structure/server/overview>

Also Portfolio for Jira can also help

<https://marketplace.atlassian.com/plugins/com.radiantminds.roadmaps-jira/cloud/overview>

comments: author: sudheer
body: Hi [@Suhas P](/t5/user/viewprofilepage/user-id/734010)

I can't define the hierarchy under Epic using Portfolio for JIRA, We can define the hierarchy above Epic.


author: drB
body: I wonder why Atlassian is sticking to a fixed hierarchy epic-user story -task? It's not agile at all to do so but more just annoying. With other issue management systems, you set up in seconds any hierarchy you want....


Tags: advanced-roadmaps
How can I use portfolio with estimation of effort instead of story points?
Asked by Dima Salman:

Hello,

I am on a trial version of Portfolio. We usually use Kanban boards with release versions. Our due dates are based on the original estimates that are added by developers. My need is to be able to view the releases in the form of a project plan just like Portfolio displays them but nevertheless I could not.

I want to ask please where does the scheduled start come from? Why do issues extend along the timeline as a whole although I added a target start and a target end?

Moreover, is it possible for Portfolio to arrange the issues on the schedule based on the original estimate and according to the rank in the kanban without having to manually insert the start date and end date? This will make our day to day work much easier.

Thank you


Answers:
author: Earl McCutcheon
body: Hello Dima,

The Scheduling behavior comes from a few different locations for the calculation, and is covered in mode detail here:

- <https://confluence.atlassian.com/jiraportfolioserver/scheduling-behavior-802170552.html>

The Placement of the issue in the timeline (Stretching across the timeline) is the calculated Scheduled start to end time. The Target Start and Target End dates as apposed to the Scheduled Start and end dates are an indicator of planed vs actual the target being Planed and the Scheduled being based on calculations of the other inputs the actual amount that can be applied based on the variable inputs. This will give you an indicator if a goal can be met or if you will come in under goal.

Additional details on the target Start and End dates is covered here:

- <https://confluence.atlassian.com/jiraportfoliocloud/add-target-start-and-target-end-dates-868977060.html>


Tags: advanced-roadmaps
Tasks created in Portfolio are not shown in the Project
Asked by Lasse Schmitt:

Hello,

I really Like portfolio, but I have one problem.

Once imported to Portfolio, I created Stories and Sub Tasks.

Unforutnately, all new Tasks and Stories created within Portfolio are not shown in the project which means I can't mark them as "Done" or do anything else like attaching files etc.

Can you help me?

Attached a few Screenshots.

Thanks a lot for your help!

![Bildschirmfoto 2018-04-18 um 10.22.27.png](/t5/image/serverpage/image-id/19962iA227F4DBCCFD3CEB/image-size/large?v=v2&px=999 "Bildschirmfoto 2018-04-18 um 10.22.27.png")![Bildschirmfoto 2018-04-18 um 10.23.31.png](/t5/image/serverpage/image-id/19963i7E0672A90371EA2B/image-size/large?v=v2&px=999 "Bildschirmfoto 2018-04-18 um 10.23.31.png")


Answers:
author: Krista Parker
body: Hmm, did you commit your changes to Jira after you added the stories in Portfolio?


Tags: advanced-roadmaps

developer
License issue
Asked by William Flynn:

Silly me - I bought the license for Portfolio, Client, Jira, and Confluence but did not already have them installed. Soooo, the license install failed, and now after installing the products using the free trial, it wants me to buy new licenses. I can't seem to find a way to install the licenses I already have.

It's gotta be there somewhere... help?


Answers:
author: Andy Heinzer
body: Your licenses are available to you when you login to [https://my.atlassian.com](https://my.atlassian.com?) provided that you are logged into this site with the same email address that you used to purchase these licenses.

Within Jira, you can activate the Jira Software, Jira Service Desk, and/or Jira Core licenses at the \[Your Jira URL\] /plugins/servlet/applications/versions-licenses address

However for plugins like Portfolio, you would need to use the UPM in Jira to activate these licenses. This can be done under the specific plugin name found on \[Your Jira URL\] /plugins/servlet/upm

Confluence can also activate the license by:

1. Go to ![](https://confluence.atlassian.com/doc/files/747833194/747833195/2/1517274813281/cog.png) \> **General Configuration**.
2. Choose **License Details** in the left-hand panel.


author: Daniel Eads {unmonitored account}
body: Hi William,

It varies per product. Here's links to the documentation for installing the license for each of these, and if you're still having trouble we can try addressing each piece individually. If you don't have the licenses you purchased handy, they can be retrieved at <http://my.atlassian.com>

* [Jira](https://confluence.atlassian.com/adminjiraserver/licensing-your-jira-applications-938847718.html)
* [Confluence](https://confluence.atlassian.com/doc/managing-your-confluence-license-313467774.html)
* [Marketplace plugins (Portfolio for Jira, Jira Client, etc)](https://confluence.atlassian.com/jirakb/how-to-update-your-add-on-license-429916493.html)

Cheers,  
Daniel


Tags: advanced-roadmaps
How to see the factors that affect scheduling of a particular item?
Asked by Kosh Sarkar:

In the Scope view and seeing hierarchy level of Stories, I thought that if I click on one of the stories to view the details, I should be able to see a section called 'Scheduling Factors', which list out factors used to schedule the item. Right now, I can see 'Dependencies' and 'Scheduling' but not 'Scheduling Factors'. Is there something I need to do to see this?


Answers:
author: Kosh Sarkar
body: What I see is the following, where the 'Scheduling' section is the last section visible.

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

I am referring to this 'Scheduling factors' section seen in this link - <https://confluence.atlassian.com/jiraportfolioserver/scheduling-behavior-802170552.html>

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

Is the above only available on Portfolio Server?

comments: author: Tzu Hau Chai
body: just compared Cloud vs Server, indeed the section is available on Server only. Here's the documentation for portfolio cloud, the scheduling factors is not mentioned here: <https://confluence.atlassian.com/jiraportfoliocloud/scheduling-behavior-828785428.html>


author: Kosh Sarkar
body: Thanks for the response - is there a reason this info isn't available on Cloud? Looks like really useful info to have when trying to understand how an item is scheduled, or can be moved.


author: Tzu Hau Chai
body: Could you attach a screenshot to show how the section looks like on your end? and what portfolio version are you using?


Tags: advanced-roadmaps
Unable to create a Plan in Portfolio
Asked by ????:

I have successful configured the Initiatives hierarchy in Portfolio which is an optional step.

But unable to even view a "create Plan' button using Jira Cloud.


Answers:
author: Tzu Hau Chai
body: Go back to the System Dashboard, click "Portfolio" on the sidebar and you should see the "Create Plan"

![createplan.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/19779i2EA1302745FDFEF9/image-size/large?v=v2&px=999 "createplan.PNG")

comments: author: ????
body: The issue was an access level.., Administrator wasn't enough.

Thanks.


Tags: advanced-roadmaps
Where do I set the number of hours in a day in the latest version of the jira Application ?
Asked by Lornette Palmer-Rhoden:

![trying to configure hrs per day in the LATEST jira app.png](/t5/image/serverpage/image-id/19745iDDC9B58510B9E249/image-size/large?v=v2&px=999 "trying to configure hrs per day in the LATEST jira app.png")


Answers:
author: Mikael Sandberg
body: I assume you are talking about Working hours per day, which is set under Jira Settings \> Issues \> Time tracking

![Time tracking - JIRA.png](https://community.atlassian.com/t5/image/serverpage/image-id/19752i939B9CEA85E197AA/image-dimensions/600x455?v=v2 "Time tracking - JIRA.png")

comments: author: Lornette Palmer-Rhoden
body: Thanks for your very quick response, however, the version of jira that I have, I am NOT seeing time tracking as an option, see attached supporting screen views of what I am

seeing when I click on Settings.

![issue_timetracking_1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/19811i109D7DE8EFEC4EC2/image-size/large?v=v2&px=999 "issue_timetracking_1.jpg")![issue_timetracking_2.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/19812iB1D36F4183D59ACF/image-size/large?v=v2&px=999 "issue_timetracking_2.jpg")


author: Mikael Sandberg
body: You are looking at the project settings, the time tracking is set under the Jira settings. From the Jira home, go to Settings \> Issues \> Time tracking. You need Jira admin permission in order to see it.

![timetracking.png](https://community.atlassian.com/t5/image/serverpage/image-id/19865iE4E24BD15802E712/image-dimensions/530x487?v=v2 "timetracking.png")


author: Lornette Palmer-Rhoden
body: Thanks understand, this guide actually works beautifully.


author: Jaime Fraina
body: We don't use days on our projects, just hours. I tried setting the number of hours in a day to a really high number but now all estimates are showing in years instead.. I went back here to update it and now my global time settings are gone. Any ideas on what's going on here?

![Screen Shot 2020-01-15 at 10.29.05 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/79162i9AA1C2CBD858A5AC/image-size/large?v=v2&px=999 "Screen Shot 2020-01-15 at 10.29.05 PM.png")


Tags: advanced-roadmaps
How can other standard JIRA fields be added to the Portfolio Scope View table?
Asked by Gerd Suppan:

Some standard JIRA fileds can be added to the Portfolio Scope View table (e.g. components, label), but some are missing (e.g. reporter, assignee, priority).

How can those missing fields be added (I guess those can't be added by 'custom fields')?


Answers:
author: Gerd Suppan
body: Thank you for your fast answer.

The linked suggestion is in the status 'open' since 2015!

In your workflow you have two ways to get it into the backlog, one direct step and anoher over verification.

So my question is how can we get it into the backlog?

Thank you, sincerely

Gerd


author: Tzu Hau Chai
body: It is still not possible to add the JIRA fields you mentioned in the scope view: <https://jira.atlassian.com/browse/JPOSERVER-193>

you can use some third party plugin's scripted custom field (which can be added to the scope view) to pull data from the JIRA fields you mentioned, but this is not really an elegant solution.


Tags: advanced-roadmaps
Why can't I sort by Assignee in Portfolio for JIRA
Asked by Parker Van Dyk:

We are wanting to sort by Assignee in portfolio. Our Assignee's are the project managers for the specific epics and it would make our lives much easier if we bring an Assignee column in. Let me know if y'all have any suggestions or workarounds.


Answers:
author: Tzu Hau Chai
body: Assuming you are referring to the field columns in the scope view, it is still not possible to add the assignee field: <https://jira.atlassian.com/browse/JPOSERVER-193>

you can use some third party plugin's scripted custom field (which can be added to the scope view) to pull data from the JIRA fields you mentioned, but this is not really an elegant solution.


Tags: advanced-roadmaps
Ability to reorder columns on the Scope page
Asked by Dennis Crow:

Is there a way to reorder the columns on the Scope page in portfolio? It can be difficult to get all the columns I want displayed on a reasonable sized monitor!.

I'd like to be able to put the most important columns (like status) on the second or third column, not on a column on the far right.


Answers:
author: Tzu Hau Chai
body: currently its still not possible to reorder column, here's the feature request: <https://jira.atlassian.com/browse/JPOSERVER-497>


Tags: advanced-roadmaps