youngmon/atlassian-qna huggingface dataset:
Writing plan back to board
Asked by markus spinnenhirn:

Hi community. We do some tests with portfolio to make planing sprints more easy and to give stockholders a better overview of the next iterations.

We have already a board for our project and already some sprints. The sprint we are working right now is started and I see the sprint in portfolio.

I was now playing around and reorder the EPICS for the next iterations. The calculation of portfolio worked like expected and I have a result for the next iterations.

But how can I write this information back to the sprints? Do I really have to go through all EPICS (and maybe issues if the EPIC is scheduled to multiple sprints) and change the value in the sprint column by hand? It is calculated and I want to use it like that.


Answers:
author: Phil
body: Hi Markus,

which fields/values do you want to overwrite in JIRA?

Regards,

Phil

comments: author: markus spinnenhirn
body: Hi Phil,

mainly the sprint on the issues which are part of the next sprint (on which the developers must work next).

I was planing my next sprint with Portfolio by rearranging the priority of the EPICS and now it would be nice to "fix" the next sprint.

I know I can add "Teams" in the scope of a plan and then change each sprint from "calculated" tho the sprint. But with a lot of EPICS and issues that is a lot of work.

Regards,

Markus


author: Phil
body: Hi Markus,

did you find a solution for your problem?

Are you able to commit your changes from Portfolio to JIRA?

Regards,

Phil


author: markus spinnenhirn
body: Hi Phil,

I didn't find a solution yet. I still go through all EPICS for the sprints I want to finalize and change them manually. Then I can commit my changes.

Regards,

Markus


Tags: advanced-roadmaps
How to filter stories only from one release in scope view?
Asked by Dorota Wojaczek:

I created plan in Portfolio that contains 2 releases: A, B. I have got a future sprint for a team in JIRA that contains 2 stories in release A, 2 stories in release B and 3 issues not related to any release. In Portfolio in Scope view I set Story and Release A in filters. The problem for me is that 2 stories from release A and 3 issues not releated to any release are shown. How can I filter issues only assigned to release A? It is important for me to see all issues in sprint but also to have opportunity to see issues only from selected release.


Answers:
author: Phil
body: Hi Dorota,

are the 3 stories which are not assigned to a release (in your case release A and B) to the "Later"-Release? In this automatically generated release you should find issues that are not scheduled and therefore not part of the schedule view.

Regards,

Phil

You can find details on the "Later"-Release here:

<https://confluence.atlassian.com/jiraportfoliocloud/using-the-later-release-828785326.html>


Tags: advanced-roadmaps
Skipping hierarchy with Initiatives/ Portfolio
Asked by Jam:

Hi Atlassian Team,

while checking out Portfolio I have a question about **grouping issues/ big picture** with initiatives:

1. We allowed the ticket type "initiative".
2. Sometimes I want to assign STORIES, which are not part of an EPIC, to INITIATIVES anyway.
3. By doing this I attempt to break the hierarchy Initiative \> Epic \> Story.
4. It seems to be impossible.
5. But sometimes it makes, if it is a rather small thing that does not justify an epic.
6. Or do I have to use a dummy wrapper epic in this case?

Side question on **setting up Initiatives**:

1. I found the tip online to create a dummy project for initiatives only so that this managementy level of info does not interfere inside my actual project.
2. (Also how you set up Jira + Portfolio for multi-project usage?!)
3. When I tried to add the main project and the dummy project to Jira Portfolio, I got an error message that initiatives as a type are in no selected project.
4. Error only went away when I allow Initiatives in the main project directly.
5. But then, initiatives can be selected as ticket type and initiatives appear as backlog items in main project -- undesirable.

I would love to get some guidance here.

Thx  
Jam


Answers:
author: Phil
body: Hi Jam,

as far as I know, it is not possible to break the Initative \> Epic \> Story hierarchie.

Regarding your second question:

There are two ways:

1. Add several projects/boards from JIRA to a plan in Portfolio.

2. Use only one project per Portfolio plan and create a program for an overview:

<https://confluence.atlassian.com/jiraportfolioserver/programs-931037964.html>

<https://confluence.atlassian.com/jiraportfolioserver/creating-and-deleting-programs-931037970.html>

Regards,

Phil


Tags: advanced-roadmaps
Must an epic end within a single release?
Asked by Michael Kogan:

Dear Community,

Is it recommended to span an epic over more than one release? I have epics that contain stories some of them cannot make it into one release. Should I create a new epic for those and assign the new epic to the new release?

Thanks,

Michael


Answers:
author: Phil
body: Hi Michael,

instead of creating a new epic you can also assign more than one release (or fix version in Portfolio) to the epics. Does this help you?

Regards,

Phil

comments: author: Michael Kogan
body: Thanks Phil,

Unfortunately this does not help: if I have an epic with a story that goes into release N and another story that goes into N+1 and I assign the epic to both releases then there is no way for me to rank the epic so it satisfies priorities in the two releases.

My question was a general one: is it a good practice to have epics that span two releases or the guideline is to restrict an epic to a single release?

Michael


Tags: advanced-roadmaps
Multiple teams using one project
Asked by Chris Gagn?:

Hello,

Most organizations using JIRA create one project per team. However, I am also aware of some organizations that have multiple teams using one project. They then use labels or components to filter out their Scrum boards.

Does this work well with JIRA Portfolio? Can multiple teams share one JIRA project, then separate teams into different Scrum boards and logical teams in JIRA Portfolio using labels and/or components? If it does work, what are the pitfalls if any?

Thanks!


Answers:
author: JCameron@peopleschoicecu.com.au
body: Seeking the same answer Chris.

I have 12 projects, of this one project in Jira has 4 teams using components to filter 4 boards and sprints for each team.

I need to find a way for Portfolio to report for each board, so I have created 4 teams in portfolio and assigned each a board for their scope. Portfolio doesn't seem to like this as it is not reflecting the correct scope and backlog items are not accurate. Items are missing and the results change depending on how you apply Portfolio out of the box filters.

Did you ever get your answer?

Cheers Jas


Tags: advanced-roadmaps
Is there a way to move/remove an issue from a Release in Jira?
Asked by Michelle Jackson:

We have a release that we would like to wrap up, there are 2 issues that we have decided are not necessary for this particular release and we would like to roll them into our next release. How do we move them from one release to the next?

Thanks in advance!

Michelle


Answers:
author: Petter Gon?alves
body: Hello Michelle,

Welcome to Atlassian Community!

You just need to navigate to the issue and edit the **Fix Version/s** field, removing the current release and adding the new one as you want.

For more information about this feature, check the documentation below:

- [Managing Versions](https://confluence.atlassian.com/adminjiracloud/managing-versions-776636296.html)

Please, let me know if it works for you.

comments: author: William Burrows
body: Good Afternoon,

The fixed version field is not editable. even when I go to edit the issue and add all of the fields, it is not a field. The fixed version only shows a link to the version, and wont let me remove it from an issue


author: Petter Gon?alves
body: Hello William,

In order to set a fix version to an issue, you must have the permission to **resolve issues** in the project:

![Screen Shot 2019-05-21 at 11.16.20.png](https://community.atlassian.com/t5/image/serverpage/image-id/55282i03D48B7FC575D43A/image-dimensions/500x51?v=v2 "Screen Shot 2019-05-21 at 11.16.20.png")

Once you have this permission, you can drag the mouse over to the fix version field and a pencil icon will appear to edit it:

![Screen Shot 2019-05-21 at 11.27.44.png](https://community.atlassian.com/t5/image/serverpage/image-id/55283i2780CFF3940E7D69/image-dimensions/496x212?v=v2 "Screen Shot 2019-05-21 at 11.27.44.png")

If it didn't work, try to use a different browser or incognito mode just to ensure you are not facing a cache problem.

Let me know if this information helps.


Tags: advanced-roadmaps

release
How to display ALL Issues in an Epic -
Asked by Michelle DelVecchio:

I can currently only see 7 issues listed when there are over 30 for an epic


Answers:
author: CARLISLE
body: You can Hide Epics Panel and Hide Epics Labels. Make sure that setting is ++not wrong++ on the right hand side of the tool bar under the Board bar.

On the left, you can see the all the EPICS from the ferst button.

Also, make sure you don't have a ++wrong filter++ taking all the goods so to speak from your data query.


Tags: advanced-roadmaps
How do you match the two categorization possibilities "themes" in Portfolio and "label" in Jira?
Asked by C. K.:

I'm looking for a good reference in how to finde the link between our generic Jira project and the possibilities in Portfolio when it comes to categorizing issues.

By now the "best" way is categorizing by label in Jira and then add the fitting theme in the Portfolio view. I think that's a lot of manual work and I also don't really see that as a task for a single person.

A good scenario would be a direct link between what I have as a theme in Portfolio and the labels I use in the projects.


Answers:
author: Jason Golden
body: I think Atlassian sensed this tension when designing the [new experience](https://confluence.atlassian.com/jiraportfolioserver/portfolio-for-jira-new-experience-952623566.html). Themes have seemingly been retired in the new experience in favor of "group by" and "color by" and using the planning view as your report, although they are working on additional reporting options (thus the tab is gone).

For now, you can color by label, so it seems label is the way to go now (for better or worse). I suspect they will also add structured data options for custom fields in the future, as their documentation on color by priority suggests. <https://confluence.atlassian.com/jiraportfolioserver/customizing-view-settings-962968240.html#Customizingviewsettings-labels>

comments: author: Jason Golden
body: Update! This was improved in 2.24 to allow for color by single select list and multi select list. <https://confluence.atlassian.com/jiraportfolio/portfolio-for-jira-2-24-release-notes-966036854.html#PortfolioforJira2.24releasenotes-colorby>


Tags: advanced-roadmaps

label

theme
JIRA Portfolio Ignoring Priority
Asked by chadsmom:

I'm confused why JIRA portfolio is ignoring the priority in my scope table. Here is my issue right now:

* I have 33 Epics planned out for the year, in priority order, with releases assigned to each one. Currently releases are based on Quarters.
* I set a "Target End" for every item
* I will have 5 total teams working on this project

The problem I'm having is Portfolio seems to be completely ignoring my priority for one of my Epics. Out of the 33 Epics, it's currently listed as #3 in the list with a release date of Q1. The amount of work is slightly more than 1 sprint for the team the is working on it based on their calculated velocity. However, no matter what I do, Portfolio continues to schedule this Epic spanning over 6 months, and prioritizes items lower than it to be finished earlier.

How can I enforce the priority scheduling? I don't want to set up hard dependencies since I want to be able to start other features without a dependency needing to be 100% complete. I'm confused why Portfolio isn't scheduling the work for my #3 priority Epic to be finished before the others.

Happy to provide the settings I'm using if that will help.


Answers:
author: chadsmom
body: I ended up figuring this out through some trial and error. Portfolio will ignore your Epic rank ++if++ that Epic has children stories assigned to it. Since I had some stories created for one of my epics and they were at the bottom of the backlog in JIRA, this essentially trumped my Epic ranking and it used the ranking of the children, thus making it the **last** ranked Epic in Portfolio even though it was #3 in the list. This is why it wouldn't schedule it ahead of others.

I really wish there was an option for Portfolio to be the source of truth for ranking and apply that ranking to all of its children, which could then be committed to your JIRA backlog. That would make prioritization from a higher level much, much easier, and make Portfolio more useful in my opinion.

comments: author: Wendi Pannell
body: Have you found any add'l findings with this issue. We are having a similar issue. It's also very difficult since when you look at portfolio everything looks like it should be in order - only to find a child that doesn't even show up in portfolio is messing up your prioritization.


Tags: advanced-roadmaps
Extra issue types are being changed by Portfolio for Jira
Asked by Brian:

**Background information:**

Using Jira 7.6.3 with Portfolio for Jira 2.21.0 and we have the "new planning experience" turned on.

**Problem statement:**

Unrelated issues are being changed by Portfolio when I review changes and have the opportunity to commit them to Jira. If there is no direct parent-child relationship between an issue, it makes no sense to me that Portfolio changes data for that issue. See pictures below.

**Plan details:**

I've created a plan with the following issue type hierarchy:

![Hierarchy levels.png](/t5/image/serverpage/image-id/42666i141FC45D3383F25E/image-size/large?v=v2&px=999 "Hierarchy levels.png")

The source issues for my Plan are:

![Issue sources.png](/t5/image/serverpage/image-id/42667iDFB1749A635BBDB3/image-size/large?v=v2&px=999 "Issue sources.png")

My plan before clicking "Review Changes". Note how I have 3 epics with a handful of stories in each. 2 epics have the same parent Initiative and 1 epic has a different parent Initiative. Both of my Initiatives are tied to the same Product and this Product is tied to 1 Portfolio which is tied to 1 LoB as the hierarchy I've made dictates.

![Before review changes.png](/t5/image/serverpage/image-id/42668iD318E3D7B512DDF5/image-size/large?v=v2&px=999 "Before review changes.png")

Picture of all the issues that Portfolio is trying to change that don't make sense to me. I've pointed out a few that should have nothing to do with this particular plan.

![review changes screenshot.png](/t5/image/serverpage/image-id/42669iF87B641A45D5EBDD/image-size/large?v=v2&px=999 "review changes screenshot.png")


Answers:
author: samrobertsofficial
body: Hi [@Brian](/t5/user/viewprofilepage/user-id/2433164),

From what I can tell, it looks like these changes happened due to using optimize, is this correct?

We've looked into it, and it appears to be a bug. There shouldn't be a new change created when the date doesn't change. We've added this to our backlog as something that must be fixed. I can't say for sure when a fix will be released, but I'll reply to this when it is made.

I know this isn't ideal, but for now you can discard the changes that don't make sense.

Thanks for letting us know about this issue,

Sam

comments: author: Brian
body: Hello Sam,

That's correct. I hit optimize and then after I do that there's a button that comes up (which you can see in my 3rd picture) labeled "Review changes". When I click that, that is when I begin to see all these other issues come up that have no relation to my plan.

As you can see in my picture, I have a really simple demo plan built up with a demo Jira project. Only 3 epics, a handful of stories for each epic and a couple Initiatives for each epic. You can see my hierarchy in the picture above too.

Honestly I'd rather have it be a bug then something I'm doing wrong. It's troublesome because of some of those related issues have Assignee's with notifications turned on, they receive email's everytime I do something which they complain about.


Tags: advanced-roadmaps
Issues not appearing in Jira Portfolio resource plan
Asked by christopher.rhymes:

I have a portfolio plan based on a custom filter which includes specific projects.

When I view the custom filter, the new issues I have created are shown and they all have time estimates against them.

When I go into portfolio only one of the issues for the project are displayed in the plan. I cannot see any difference between the issues that don't display and the one issue that does display.

I have cleared all of the filters I can see from the plan view but they still don't appear?


Answers:
author: Earl McCutcheon
body: Hi Chris,

Check out this previous post in the comment by Martin that has a great check list of varying items that could be the source of the issue:

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

Regards,  
Earl

comments: author: christopher.rhymes
body: Hi Earl,

Thanks for the link. The filter for Teams was on which was hiding the issues, so some progress being made, but the time estimates are not being pulled through from the issues?

Thanks,

Chris


Tags: advanced-roadmaps
Not able to drag & drop using the "new planning experience"
Asked by Luk Lau:

Hi all,

When I enable the "new planning experience", I am not able to drag and drop to schedule the issues (the issues also have a "stripe" bar)

Can someone help me to figure out why?

Thank you for your help!

Luk :)  


Answers:
author: samrobertsofficial
body: Hey [@Luk Lau](/t5/user/viewprofilepage/user-id/2564420),

Thanks for trying the new experience out. It sounds like you are inside the 'optimise' view because of the striped bars. Drag and drop is not possible in this view because it is a preview of Portfolio's scheduling algorithm.

You can either:

1. "Cancel", and this will return you to the regular view.

2. "Apply changes" from optimise. This will not affect your data in Jira until you review \& save changes.

After one of these, you'll be in the regular roadmap view where editing is possible.

Let me know if this answers your questions, or if you have any more feedback on the new experience.

Thanks,

Sam


Tags: advanced-roadmaps
Show several hierarchy levels in Schedule
Asked by Phil:

Hi everyone,

we have a Saga-Epic-Story structure in our project.

Is it possible to choose "Saga" as a hierarchy level and then seeing the inherent Epics and Stories in the schedule?

Thanks in advance and regards,

Phil


Answers:
author: Earl McCutcheon
body: Hi Phil,

In the Live Plan View no, only the current hierarchy level is going to be displayed in the schedule roadmap timeline section, You can expand the issues in the Scope section to see additional details of the hierarchy but the Schedule will still display the currently selected hierarchy.

But in the [Portfolio New Experience](https://confluence.atlassian.com/jiraportfolioserver/portfolio-for-jira-new-experience-952623566.html) you can expand from the top initiative down through the full hierarchy and have the issues displayed in the roadmap schedule timeline.

I would recommend switching to the new experience view to check it out, and you can switch back to the current view at any point, additional details on the changes can be seen at the link below, but no note the New experience is still rolling out and still has a few missing features such as the reporting covered in more detail in the changes:

* [Changes in the new experience](https://confluence.atlassian.com/jiraportfolioserver/changes-in-the-new-experience-961780550.html)

Regards,  
Earl

comments: author: Phil
body: Hi Earl,

thank for your answer.

At the moment, we can't use Portfolio New Experience but maybe in the future.

Now, I am experiencing that Portfolio shows (for an unknown reason) more than one hierarchie level in the schedule as well as the target schedule. Although in the Scope-table below, only User Stories are shown, we find Sagas and Stories in the Schedule. Do you know why this is happening?

Thanks and regards

Phil


author: Phil
body: Hi Earl,

I think I found the reason why several hierarchy levels are shown in the schedule.

Changig to the Epics hierarchy shows all scheduled Epics + scheduled Sagas that have no child issues (such as Epics). Did you experience the same?

Regards,

Philipp


Tags: advanced-roadmaps
Timetable and PM work
Asked by Phil:

Hi everyone,

we are working with Jira Portfolio to set up a timetable and do some PM work.

Any suggestions how to have issues scheduled just by entering a target start and target end without any estimation and without assigning them to a release/team?

Thanks in advance

Phil


Answers:
author: Earl McCutcheon
body: Hi Phil,

Switch from Schedule to **[Target schedule](https://confluence.atlassian.com/jiraportfolioserver/adding-target-dates-868977194.html),**and the un-estimated Issues will show up light blue on the timeline lining up with the target dates like this:

![Screen Shot 2019-01-16 at 4.30.47 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/42697iD3C714B350982F44/image-dimensions/514x86?v=v2 "Screen Shot 2019-01-16 at 4.30.47 PM.png")

Regards,  
Earl

comments: author: Phil
body: Thanks Earl, that helps :)


author: Phil
body: Hi Earl,

as you mentioned the issues don't show up in the Schedule view, but are visible in the Target Schedule view. Do yo know why they now neither show up light blue nor dark blue but in white? The issues are not estimated and are not allocated to a team.

Thanks and regards,

Phil


Tags: advanced-roadmaps
Get members of a Team in Portfolio through coding.
Asked by David Henriksson:

Hi!

We have the Scriptrunner plugin and I want to retrieve all the members of a Portfolio team through scripting. I have tried with the rest-api <https://docs.atlassian.com/portfolio-for-jira-server/REST/2.13.0/teams/> but it looks like there is no way to get resources from a particular team.

Is it even possible to get members of a Portfolio team through coding?


Answers:
author: Earl McCutcheon
body: Hi David,

You can pull the TeamID and PersonID from the [GET /resource endpoint](https://docs.atlassian.com/portfolio-for-jira-server/REST/2.13.0/teams/#/definitions/TeamDTO):

```
http://BASE_URL/jira/rest/teams-api/1.0/resource
```

Regards,  
Earl

comments: author: David Henriksson
body: Oh, missed that one. Great, thanks :-)


author: Rolando Dorbecker
body: by any chance were you able to get good results by using the /resource , i am being trynig but the /resource is not bringing all the team , person relation that i can see on the UI


Tags: advanced-roadmaps
While creating portfolio plan with filter by label, the plan doesn't show the epics hierarchy
Asked by Tanya Barsky:

While creating portfolio plan with filter by label, the plan doesn't show the epics hierarchy.

E.g.

filter: labels in (security), brings to the plan tickets on the story level with such a label, but doesn't bring epics with this label.


Answers:
author: Phil
body: Hi Tanya,

are the epics shown in the plan without the filter by label?

Best,

Phil

comments: author: Tanya Barsky
body: yes, if I do filter by epics only, like key in ("epic num")


author: Phil
body: Which hierarchy level view did you choose then?


author: Tanya Barsky
body: Epics, stories, subtasks?


author: Phil
body: See bullet point 1:

<https://confluence.atlassian.com/jiraportfolioserver/scheduling-and-timeline-802170550.html>

Does the chosen hierarchy level make a difference in the view?


Tags: advanced-roadmaps