youngmon/atlassian-qna huggingface dataset:
Colaborating on Features with Customers
Asked by Tomasz Guja:

Hi,

Currently we are using JIRA Software and SD. I'm just testing the Portoflio and I have question. Obviously by SD I can gather customer suggestions, create linked tickets for dev projects and than manage releases from Portfolio.

But is there a way to:

* for customers to raise some suggestions (for example by e-mail) that will land to some set to Portfolio so that the Product Owner can review them and assign them properly?
* for customers to be able to see some portfolio road map (without spending JIRA paid license for them)

?

Basically what I consider is to replace the ProductBoard product by some Atlassian solutions, but I have to be sure that the basic feature set can be replaced.

Regards


Answers:
author: Thomas
body: Hi [@Tomasz Guja](/t5/user/viewprofilepage/user-id/156618),

* Portfolio plan are based on issue sources (Project, Boards, JQL) which means as long as this issue source captures the suggestion then those would show up in your Portfolio Plan.
* Portfolio permissions work based on Jira user groups which would not allow you to define an Anonymous access. It would be possible to build on top of the Portfolio export function but that would require some effort on your side. Portfolio Server latest version includes an IssueInPlan JQL function that would allow you to use the JIRA search API to expose the suggestions.

Cheers,

Thomas

comments: author: Tomasz Guja
body: Thanks [@Thomas](/t5/user/viewprofilepage/user-id/58170). But unfortunately this is quite bad news, as this means it's limit rather to internal usage only, when ProductBoard which we are using also works partly for customers. I really wish Atlassian will develop Portfolio for this area, so it looks like nice but basic tool.

Regards


Tags: advanced-roadmaps

collaboration

customer

feature

release

roadmap
Working hours and days management in Portfolio
Asked by Sigita Martinaityte:

Hi,  

What happens with the teams capacity if the same Public holiday is added both through the configuration of Development of Roadmap in "Working hours and days management" and through Teams absence management? Will the system recognize that this is the same day and ignore this, or will the hours be deducted twice?


Answers:
author: Thomas
body: Hi [@Sigita Martinaityte](/t5/user/viewprofilepage/user-id/1178568),

Portfolio uses those data to define the team members availability, holidays which applies to all teams and members of a plan have precedence over absences and exceptions.

This means the capacity of the teams and team members during a holiday will be 0 and not any lower even if there are additional absences on that day.

Cheers,

Thomas

comments: author: Sigita Martinaityte
body: Thank you! This helps :)


Tags: advanced-roadmaps
Capacity and Planning: Tasks Estimated for week (h) 8 + 8 + 8 + 8 + 10 = 32h for week, why?
Asked by Mirek:

Hi everyone!

Pretty sure that it is a really simple question and I'm still evaluating Portfolio mainly for release planning and capacity overview, I do struggle with one weird behaviour I get:

* 5 tasks planned for 1 developer for 1 week:
* 4 task for 8h (FT)
* 1 task for 10h

When calculating Portfolio shows me a **32h capacity used** for the defined week and it moved that **10h task for the next week**.

Question: why I can't have him work on, let's say,**Friday for 8h** and resume on **Monday** next week with the **leftover of 2h**?

Many thanks for help!


Answers:
author: somethingblue
body: Hi Mirek,

There is a Suggestion that may help understand this behavior at [Allow portfolio to book stories into sprints if any capacity is available](https://jira.atlassian.com/browse/JPOSERVER-1867).

The logic is the Full capacity need to be available and the velocity is 40h for the user and the 8+8+8+8+10=42 so one full issue pushed, but a way to get more out of this is the priority arrangement as covered in [Scheduling behavior](https://confluence.atlassian.com/jiraportfoliocloud/scheduling-behavior-828785428.html):  
> The scheduling algorithm currently optimizes the scheduling of highest priority items first. Even if there might be a scenario where the team could fit in a bit more capacity into a release if it started with a lower priority item, Portfolio for Jira will not suggest this in the schedule. Items that have the highest priority should also be started first. Also, you might want to prioritize items with the highest risk first to tackle uncertainty early in the process.

See if this works for you:

Break the 10 into two issues as an 8 and a 2 hour and prioritize the 8 hour portion above the 2 hour portion. The 2 hour portion will be moved and the 8 will fill capacity.

> **Example**: 8 hours scheduled on the main issue and 2 hours scheduled to a second issue set for Follow up on issue 1

Take a look at [JPOSERVER-1867](https://jira.atlassian.com/browse/JPOSERVER-1867) and if you believe that fits this scenario please vote on it and add your use case to the comments. Let me know if that helps.

Cheers,

Branden


Tags: advanced-roadmaps
Should Themes/Initiatives be visible in the backlog?
Asked by Naomi Perez:

Hello All,

I've heard that themes/initiatives should not be visible in a backlog. Is this true? Am I supposed to configure a separate workflow for Initiatives/Themes?

For context: I was able to configure Epics/Stories/Task, and I understand that I can assign themes/initiatives to these, but what if I don't want them displayed in (and cluttering) the backlog?

I'm still new to JIRA so I hope these questions make sense!

Thanks for your help!


Answers:
author: Naomi Perez
body: This helps a lot! Thank you!


author: Tyler Brown
body: Hey Naomi,

Themes will not be visible in the backlog, they currently only exist in the Portfolio space.

Initiatives will show up in your backlog, however you can simply amend you board query to include "and issuetype != Initiative" and they won't clutter your backlog.

If you did want a way to easily see or rank your Initiatives I would suggest creating an Initiative only board.

Hope this helps,

Tyler

comments: author: Baheej Al-Khatib
body: Hello Tyler,

I am experiencing this problem currently and did as you suggested and it worked well for my board, but it also took my initiatives off of my plan that was associated with the board.

Is there a fix around this? I want to take Initiatives out of Backlog view but keep them on my plan in portfolio,


author: John Elder
body: Tyler, I found this post from 2018 and Baheej's reply from 2019... and I am having the same issue now in 2021. I have a Plan whose issue source is a board, and I want the Initiatives to appear in the Plan, but not be present in the Backlog, cluttering up the space where the prioritization occurs. Is there a workaround of any kind for this?


author: Sandesh DSouza
body: I still see the issue with no resolution. Any help is appreciated.


author: Sandesh DSouza
body: One way to do this is have a Quick filter and use that in the backlog so that you don't see in the backlog but still in the roadmaps


Tags: advanced-roadmaps

backlog

initiative

theme
delete subtask in JIRA
Asked by Dania Zaccara:

Hi all,

I notice that in Portfolio I can't remove item from plan without removing his parent issue.

I mean, when I have a story with an epic and initiative link, if this story is the only one under his relative epic, when I exclude this story from my portfolio plan, portfolio remove his epic also.

Why this behavior?

Thanks

Dania


Answers:
author: Thomas
body: Hi [@Dania Zaccara](/t5/user/viewprofilepage/user-id/181452),

What you are seeing is due to selection behavior and not really how the exclude works. You are still able to only commit the sub-task / revert the parent(s) changes in the commit dialog.

That being said, I'd be keen on having more details on what would be your expected "selection" behavior when:

1. Selecting a parent item
2. Selecting a child item
3. Selecting all of the children of an issue

Cheers,

Thomas


Tags: advanced-roadmaps
Dynamic dates fail to recalculate when velocity is changed in portfolio.
Asked by William Cipriano:

I am attempting to troubleshoot a issue for someone who is more familiar with portfolio than I so please excuse me if this question is obvious but I have spent a few hours searching for this without success.

I have a portfolio plan that contains two projects. Everything appears to have been imported correctly but when setting the release dates for versions using the "dynamic date" function briefly described [here](https://confluence.atlassian.com/jiraportfoliocloud/configuring-release-dates-828785321.html) I am unable to cause any of the dates to change in a meaningful way. For example, changing the velocity of the team portfolio simply creates more sprints between the releases while retaining the same release dates. As weeks cannot be created out of thin air this isn't very useful. Is this the intended functionality of "dynamic dates" or is there some things that I can troubleshoot that would effect them?

Thank you in advance for any assistance you may be able to offer.

I am running version 7.2.4 build 72006.


Answers:
author: Roi Fine
body: Hi William,

That's a good question. It would be great if you could attach a screen shot of the 2 situations you are describing. The dynamic date should change according to the amount of work you got planned and the team's velocity.

Cheers,


Tags: advanced-roadmaps

project
Release ordering
Asked by markkerollos:

We've recently started using Portfolio and are having a couple of issues around release structuring.

1. The order in which releases appears in both the Releases tab and the Report for Releases seems to be the wrong order. When I click and drag to the correct order this does not persist (even after committing)

2. Items which are attached to more than 1 release (because they have children in more than one release) do not appear correctly on the schedule. They appear significantly shorter (i.e. 1/8th of an iteration) than they should (i.e. 2 iterations).

Hopefully we can find a solution to this as the tool seems pretty powerful otherwise.


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

The releases order in the "Releases" tab is editable by drag-n-drop which would generate changes to be committed. The order used here is left-to-right then top-to-bottom. If you believe the ranking is not persisting for you I'd suggest trying in an incognito window or another browser to eliminate this factor, If that doesn't work I'd suggest reaching out to support (<https://support.atlassian.com/contact/>).

I'm not sure of the situation you are facing in 2., if the issues are shorter than expected it could be that their estimate is not matching the expectation or that some of the issues are being filtered out which would be another reason for them to look shorter than expected.

Feel free to share some screenshot (anonymized if necessary) to help explain the situation.

Cheers,

Thomas

comments: author: markkerollos
body: Thanks Thomas for your input.

I tried your suggestions but both incognito and different browser windows did not work.

I have managed to get it working, and the following gives more context for how this issue occurred and what resolved it.

Portfolio has 6 different projects in it.

There are 10 Cross Project releases (Release 1, 2, 3, etc.).

Only Releases 6-10 had an associated release in each project.

Releases 1-5 only had 4 of the 6 projects with linked releases.

Once I ensured that Releases 1-5 had an associated release for each project I was able to re-organise and have my changes persist.


author: Thomas
body: Thanks for sharing your solution, much appreciated!


author: Kristofer Hansson Aspman _Riada_
body: This bug covers the scenario where it is not desired to let the CPR:s create releases in all the projects that are part of the plan: <https://jira.atlassian.com/browse/JPOSERVER-2452>


author: Goden
body: I hope it can add order by releases as 1 click.

comments: author: Marcelo Gallego
body: Totally agree. Sorting by Start date / Release date is a must


author: markkerollos
body: Hi all, still hoping to get an answer on this. Cannot for the life of me work-out how to re-order the display of releases so that they are chronological.


Tags: advanced-roadmaps
JQL query on "target start" or "target end" is one day off.
Asked by Tracy Anderson:

Portfolio for Jira surfaces "target start" and "target end" on features. When I use a JQL query with those fields it is one day off. Are my dates configured incorrectly?

![Capture.JPG](/t5/image/serverpage/image-id/12617iA2C9FDF6781AC9B9/image-dimensions/514x207?v=v2 "Capture.JPG")


Answers:
author: Andrew Whitley
body: Hello [@Tracy Anderson](/t5/user/viewprofilepage/user-id/1177656), did you ever end up solving this issue? I have the same thing occurring so I was hoping you could share the resolution.

comments: author: Andrew Whitley
body: Here is the bug ticket Atlassian has for this ticket:  
<https://jira.atlassian.com/browse/JPOSERVER-2302>


Tags: advanced-roadmaps
SEARCHING: Missing portfolio dependency report
Asked by Paul Dillon:

I don't see the Dependency Report in my drop down list of reports in 'Switch report'. Dependencies are switched on. What could it be?


Answers:
author: Thomas
body: Hi [@Paul Dillon](/t5/user/viewprofilepage/user-id/541416),

If you are using Jira Cloud I'd suggest contacting [support](https://support.atlassian.com/contact/).

For Portfolio for Jira server I'd recommend updating to the latest version of Portfolio to ensure the feature is available.

Cheers,

Thomas

comments: author: Paul Dillon
body: HI,

you were right - I upgraded to the latest version and the report appeared. Thanks


Tags: advanced-roadmaps
Unable to load Portfolio plan pages
Asked by Rodrigo Vald?s:

Hi Everyone

I am working with a customer in a Jira 7.5.0 Setup with Portfolio 2.6.1 plugin. When we try to create a plan or display plan, system comes back with a message "Bummer, something has gone terribly wrong", suggesting to refresh the page (didn't work) or contact Administrator or Atlassian Support providing some kind of frontend stacktrace.

The stacktrace shows the following:

![Port08.JPG](/t5/image/serverpage/image-id/12284iE8951F8CF30F60EE/image-size/large?v=v2&px=999 "Port08.JPG")

As you can see in the picture, there seems to be an issue with jpo-wr-page-plan-scripts.js script. I did some google search and i was unable to find this specific issue anywhere, however i have found relatable issues like.

<https://community.atlassian.com/t5/Portfolio-for-Jira-questions/Error-on-some-Chrome-versions-Bummer-Something-has-gone-terribly/qaq-p/630324>  
<https://jira.atlassian.com/browse/JPOCLOUD-1998>  
<https://jira.atlassian.com/browse/JPOCLOUD-1956>

<br />

I have already tried clearing cache, changing locale, with no luck. I am suspecting that system is trying to access web to locate some resource, however this install is not able to reach internet.

Need some help in order to solve this problem.

Best Regards

Rodrigo Vald?s


Answers:
author: Thomas
body: Hi [@Rodrigo Vald?s](/t5/user/viewprofilepage/user-id/1163501),

I would first suggest trying to update Portfolio to its latest version to see if that solves the problem.

If that doesn't help it would be good to reach out to Support here: [https://support.atlassian.com/contact](https://support.atlassian.com/contact/#/)

Let me know how that goes.

Cheers,

Thomas

comments: author: Rodrigo Vald?s
body: Hey Thomas

Thank you very much for your help. I will try to update of the plugin as you suggest, and i'll let you know if that works.

Best Regards

Rodrigo Vald?s


author: Rodrigo Vald?s
body: We updated the plugin up to 2.11.0 and the exact same issue happens. Think is time to open an Atlassian Support ticket.

Thanks for your help.

Best Regards

Rodrigo Vald?s


Tags: advanced-roadmaps
Portfolio indicates there's 1 Uncommitted Change, but there's not
Asked by Terrell Teague:

Not entirely sure how/when this happened to my Portfolio plan, but I believe it occurred after adjusting some of my Team Members. After changing some people around (deleted one, changed available hours of another), I ended up with the following condition:

My Plan shows 1 Uncommitted change, even though when I go to commit it, there is nothing changed and and I get the smiley face that I'm all set.

The other condition is now I get the warning that my Plan has exceeded the 5 Year Horizon. When, actually, I don't believe there is anything actually driving it. Maybe there's one story that has some weirdness that's causing this, but I haven't found it yet.

Anyone ever experienced this?

Terrell


Answers:
author: Thomas
body: Hi [@Terrell Teague](/t5/user/viewprofilepage/user-id/1175557),

For this uncommitted changes: this is a known issue, I'd suggest having a look at <https://jira.atlassian.com/browse/JPOSERVER-1527> for status tracking and workarounds.

For the schedule hitting the planning horizon: Have a look at the estimated issues and look for an error sign in the scope table, being able to identify which issue is causing this is a good first step. The typical situation is that due to skills or just availabilities work can be started but not finished which pushes Portfolio to look further in the future until hitting the planning horizon.

Hopefully that will help.

Cheers,

Thomas

comments: author: Terrell Teague
body: The fix you mentioned for the uncommitted change did the trick, thanks!

Was eventually able to find the story that was causing my schedule to blow up thanks to your input.

Terrell


Tags: advanced-roadmaps
CustomFieldType in Portfolio
Asked by Mike Winston:

I just created a CustomField add-on for my own custom field type into JIRA, but I was not able to add it to the plan. How do i get this into portfolio? It currently says the type is not supported. Is there some API I need to implement for it to be in Portfolio?


Answers:
author: Thomas
body: Hi [@Mike Winston](/t5/user/viewprofilepage/user-id/870056),

Portfolio currently only supports a specific set of field types to ensure we are able to display and edit those correctly.

I'd suggest giving more details on what you are trying to achieve (i.e which field type and why) on the issue suggestion: <https://jira.atlassian.com/browse/JPOSERVER-155>

Cheers,

Thomas

comments: author: Mike Winston
body: Thank you [@Thomas](/t5/user/viewprofilepage/user-id/58170). I have added by item to the issue and voted it. Disappointing, but i understand.


Tags: advanced-roadmaps
Overlapping Active Sprints
Asked by Dominic O'Connor:

I'm getting an error from Portfolio that I have multiple overlapping sprints, but when I look at the sprints, they are not actually overlapping. Is this a new bug or something I'm missing?![Screen Shot 2018-01-02 at 4.37.30 PM.png](/t5/image/serverpage/image-id/11890i27D5A19EB82E3900/image-size/large?v=v2&px=999 "Screen Shot 2018-01-02 at 4.37.30 PM.png")![Screen Shot 2018-01-02 at 4.37.49 PM.png](/t5/image/serverpage/image-id/11893iCF994370A0517C51/image-size/large?v=v2&px=999 "Screen Shot 2018-01-02 at 4.37.49 PM.png")![Screen Shot 2018-01-02 at 4.38.05 PM.png](/t5/image/serverpage/image-id/11892iDD5D15D605209BE0/image-size/large?v=v2&px=999 "Screen Shot 2018-01-02 at 4.38.05 PM.png")


Answers:
author: Thomas
body: Hi [@Dominic O'Connor](/t5/user/viewprofilepage/user-id/658764),

The most likely issue is that your sprint DEMETER-RS-26 is in the past but is still active (not closed) saying that it is still running. As a result it is in fact overlapping EOS-RS-1.

If that makes sense, I'd advise to [complete](https://confluence.atlassian.com/agile/jira-agile-user-s-guide/working-with-sprints/ending-a-sprint) the DEMETER-RS-26 sprint and then reload / recalculate the plan to see if the error persists.

Cheers,

Thomas.

comments: author: Dominic O'Connor
body: Yeah that seemed to do it. Overlapping was confusing nomenclature since the end date that we defined didn't actually overlap with the next sprint, but conceptually your explanation makes sense. Thanks!


Tags: advanced-roadmaps
Automatically Set Due Date
Asked by George Birnbaum:

Im just getting set up with Jira and Portfolio after moving away from Asana. We have been used to setting due dates for when work should be completed, and while I know that due dates can be set in an issue view, how can I go about setting up due dates for issues based on the schedule created in Portfolio. Ideally, I would get a schedule for a based on capacity, make adjustments for priorities, and then when the updates are committed, the due dates would be set for items inside of the Jira issues.


Answers:
author: Thomas
body: Hi [@George Birnbaum](/t5/user/viewprofilepage/user-id/1174290),

I would suggest using the **Target start** and **Target end** date fields provided by Portfolio for this. (Docs for [Server](https://confluence.atlassian.com/jiraportfolioserver/adding-target-dates-868977194.html) and [Cloud](https://confluence.atlassian.com/jiraportfoliocloud/adding-target-dates-868977060.html)).

Cheers,

Thomas


author: Claudio Ombrella
body: I am not sure if I will be able to help here, but it is my impression that you need to enter a due date in order to do your planning - in a few words it is the other way around.


Tags: advanced-roadmaps
Add the estimation column to "Issues in Epic"
Asked by Orit Nachshon:

Hi,

Is there a way to add columns to the "Issues in Epic" view?

![2017-12-27_13-40-53.png](/t5/image/serverpage/image-id/11602i6C07D499D7391581/image-size/large?v=v2&px=999 "2017-12-27_13-40-53.png") {#toc-hId-1767558407}
-------------------------------------------------------------------------------------------------------------------------------------------------------------


Answers:
author: Tarun Sapra
body: Duplicate - <https://community.atlassian.com/t5/Jira-questions/How-do-you-add-a-column-to-quot-Issues-in-Epic-quot-panel/qaq-p/292561>


Tags: advanced-roadmaps