youngmon/atlassian-qna huggingface dataset:
Custom chart is not displaying all the data
Asked by Barbara Hernandez:

I am having problems with my custom chart, some numbers are not visible and I can't understand why since the field exists in the tickets.

I have tried with other gadgets and they work fine, but this is the only one that allow me to see the first 100 rows.

![2024-07-30 133417.png](/t5/image/serverpage/image-id/338822iEEA75FFC51C208AA/image-size/large?v=v2&px=999 "2024-07-30 133417.png")


Answers:
author: Marc - Devoteam
body: Hi [@Barbara Hernandez](/t5/user/viewprofilepage/user-id/5556374)

I suggest to refer to the vendor regarding you issue, as it seems this is a limit set by the app.

Or use multiple gadgets and adjust your sources accrodingly.


Tags: cloud

jira-server
Which field in Portfolio is linked to due date in JIRA?
Asked by Naama Lev:

*This question is in reference to Atlassian Documentation: [Importing, syncing and updating](https://confluence.atlassian.com/pages/viewpage.action?pageId=715263223)*

Hello Experts,

Can you please let me know Which field in Portfolio is linked to due date in JIRA?

Thanks

Naama


Answers:
author: Sylvain
body: None.

More details here: [JPOSERVER-1815](https://jira.atlassian.com/browse/JPOSERVER-1815)


author: Sascha Schwegelbauer
body: Also interested in the answer.


Tags: advanced-roadmaps

due-date
JIRA Portfolio: does issue time progress affect total planned time for a team member?
Asked by ???????? ???????:

Hi!

We have issues in Sprint1 in Portfolio <http://prntscr.com/8thcvy>

Part of them is only partly done <http://prntscr.com/8thd7v>

When Sprint1 will be finished, all issues that were not completed will be moved to Sprint2 (and some issues from Sprint2 will be pushed out by them to Sprint3 and so on) <http://prntscr.com/8thegt>

The question is: if the issue have 10 hours estimation and completed 90% in Sprint1 (9 hours is tracked as done) after moving to the next Spint2 (in our case) how much time will it "book" for a given team member (10 hours or 1 hour)?

@Martin Suntinger @Shafqat Bhuiyan Could you please help me to understand. Thank you!


Answers:
author: Martin Suntinger
body: Hi Vladimir,

The remaining effort which will be scheduled is always exactly the estimate visible in the backlog table. For example, if an issue had 10 hours estimate and shows 90% complete, in that moment the scheduling algorithm will still take 10 hours as the estimate to be scheduled.

The key here is that when running a plan update (Plan \> Update from Date), the remaining estimates in the backlog table are adjusted, based on the progress. Thus, if you run the plan update after the first sprint, in the update dialog you should see a suggestion that reduces the 10 hours to 1 hour based on 90% progress, and then the remaining 1 hour is scheduled, from this date onwards. the plan update also adjusts the new start date of the plan, typically you'd choose the start date of the next sprint when you run the plan update.

Hope this helps! Best, Martin


author: ???????? ???????
body: @Martin Suntinger thanks a lot. We'll experiment with it!


Tags: advanced-roadmaps
Is it possible to define due date and start date on an Epic in Portfolio
Asked by Naama Lev:

Hello,

We currently evaluating Portfolio

Our company is combined from R\&D and project implementation teams.

In order to plan our resources and project well - we need to define when a work on an Epic should to start and when it should be completed (due date)

Is it possible to define it on the Epic and Story level?

Thanks

Naama


Answers:
author: Fabrizio Galletti
body: Nope, you can only define version, relationship and earlier start date.

Online documentation has a lot of info about that


Tags: advanced-roadmaps
How can i define milestones with JIRA Portfolio
Asked by Naama Lev:

Hello Experts,

we are currently evaluating Portfolio,

We would like to manage product implementation projects, and for that we need to define milestones

Can you please advise how can I define them in Portfolio?

Thanks

Naama


Answers:
author: Jamie Cole
body: Your milestones are effectively your release dates, you could create epics for certain stages of your project and assign these to releases which match your milestone dates.

comments: author: Glenn Clapp
body: That isn't a very good approach. There can be a lot of issues tied to a milestone in different ways including:

* Cannot start until the date
* Milestone cannot be met unless issues are accepted

Those "stakes in the ground" can be moved independently of other works and may or may not impact a release. They may be a date that a tool arrives from a 3rd party or almost any other thing, and there can be many of these special dates in a release cycle.

I can see that using releases can do some of the same thing, but conceptually it is better to keep a "release" with a specific meaning and a milestone with its own specific meaning and not muddy them together.


author: Jeff Smith
body: Just some examples of dates("milestones") that are not releases.... feature/code freeze, trade show dates, scheduled maintenance on environments... to work around things, you have to be able to see them alongside your release schedule.


author: David Leal
body: It is just to add in the Gantt view similar to today?s day a vertical line for specific milestones indicating the iD or the name as a visual representation of the milestones. In 2014 it was posted the following suggestion with 125 votes: <https://jira.atlassian.com/browse/JPOSERVER-71>


author: PM
body: Please solve this issue and enable milestone visualization and add suitable features as requested with ticket[](https://jira.atlassian.com/browse/JPOSERVER-2825) [JPOSERVER-2825](https://jira.atlassian.com/browse/JPOSERVER-2825). I really don?t understand how a tool can be called advanced roadmap without adding the possibility to visualize milestones. At least it should be possible to show naming of the fix versions/releases, create abbreviation of the name and blend in/out milestones as needed.


author: Phil
body: Hi, has this matter been solved? Any other suggestion, how to add milestones in Portfolio without using releases? Thanks in advance :)

comments: author: Glenn Clapp
body: I do not see that it has been resolved. Key dates and milestones within a release are a useful mechanism.


author: Allister Scicluna
body: Please vote [https://jira.atlassian.com/browse/JSWCLOUD-20254](https://jira.atlassian.com/browse/JSWCLOUD-20254?)


author: Sofiane Hassioune
body: The issues is still not resolved unfortunately!

There is always a need to see dates different than release dates in a project plan.


Tags: advanced-roadmaps
Support for dependencies between initiatives
Asked by Rob Manger:

Hi guys,

Currently having a look at JIRA Portfolio to determine whether it meets our needs. One of the questions I've come across is that currently dependencies can only be set between Epics and Stories, not Initiatives. This does not suit our real world scenarios. Our initiatives fall into several areas, data warehousing, report generation and product development being some of the main ones. We have dependencies between all of these which we can currently not capture. These cannot be created as epics as they have different business drivers. So the question is why not have dependencies between initiatives?

Rob


Answers:
author: Rob Manger
body: Thanks for the prompt reply, Martin.

I was afraid that was going to be the answer :smile:

Cheers

Rob


author: Martin Suntinger
body: Hey Rob, we originally haven't built dependencies for initiatives as initiatives were seen as grouping elements rather than work items like epics and stories. This is why also it is not possible to add an estimate to an initiative directly while it does not have child epics, whilst the same is possible for an epic. It's been an implementation choice that constrains us now, and requires more significant restructuring in the backend to enable dependencies on that level too. We'll change that down the road, but currently the only option is really to create the dependencies between all the child epics. Best, Martin (Product Manager for JIRA Portfolio)


Tags: advanced-roadmaps
JIRA Portfolio: why stories aren't moved from sprint to sprint after one is finished
Asked by ???????? ???????:

Hi!

We created custom sprints for a team. Portfolio automatically assigned stories to sprints. But when the first sprint time was over, Portfolio didn't move stories to the next sprint and didn't signalized that we failed.

Could anybody explain why, please? What is the reason of using Portfolio if it doesn't signalize about such failure and doesn't move stories on and on.

<http://prntscr.com/868iaj> - printscreen

The same situation is with automatic sprints (sprint1 ... sprintN) <http://prntscr.com/868mak>


Answers:
author: Martin Suntinger
body: Hi Vladimir, thanks for raising this question - the way it is designed right now is that stories move on only as part of explicit plan updates (Plan \> Update from date) - this sets a new start date from when to schedule, and stories will be scheduled only from that date forward. Currently the start date of your plan is Aug 10, so work will be scheduled starting from there. If you run a plan udpate and set the new start date of the plan to let's say Aug 20, sprints before Aug 20 will be ignored and items scheduled into sprints after that.

However, all that said we're working on a tighter integration with JIRA / JIRA Agile as part of addressing our top-voted issues over the coming months (<https://jira.atlassian.com/browse/JPO-10>, <https://jira.atlassian.com/browse/JPO-42>, <https://jira.atlassian.com/browse/JPO-13>) which will significantly simplify and automate this update process. Best, Martin (Product Manager for JIRA Portfolio)


author: ???????? ???????
body: @Martin Suntinger thanks a lot. Really quick and helpful answer. You do a great job with Portfolio! Thanks once again and have a good day!


Tags: advanced-roadmaps
project portfolio
Asked by Tomasz Belina:

Hi,

Is there any way to export stories and epics created in portfolio into JIRA ? Without exporting it to csv ?


Answers:
author: Antonio Amaral
body: I'm not sure if this is what you are looking for but when you are in your project in the project portfolio you can add a column called Issue Link. When you create a new entry this field will be blank. When you clink this field for the new item you have just created you'll see an option to create a JIRA item to the Agile project. If you do this and new item will be created in the Agile project and the items will be automatically linked.


Tags: advanced-roadmaps
Portfolio: % complete using issue status
Asked by Michael McFarland:

We have been using Portfolio for about six weeks and JIRA for years. In our workflow we have a "ready for release" state that is the equivalent of resolved/closed in that we supply the value to the resolution field. I've update all the transitions to this state to use the resolve issue screen and am firing a resolve issue hook on transition. However, no matter what I do, the % complete on JIRA Portfolio only seems to update if I close the issue. I thought that this status was based on the resolution field. Am I missing something?


Answers:
author: darrenpegg
body: Is the resolution field using the same colour (Green) just like Closed does within the workflow? Just a guess that, that might be the trigger?


author: Michael McFarland
body: (facepalm) YES! That was it. This status has to be in the done category on the status edit screen. Thanks so much Darren.

comments: author: darrenpegg
body: Haha, no problem at all buddy :)


author: Chris Mitchell
body: Strange that the color is the trigger -- according to the Portfolio progress tracking page (<https://confluence.atlassian.com/jiraportfolioserver/status-and-progress-tracking-715263088.html#Statusandprogresstracking-Resolved>), the resolved field just has to be not empty.. "If the issue is resolved ( Resolution field is not empty), the progress is 100%." when there are no sub-issues.


Tags: advanced-roadmaps

jira-cloud
Recalculating in Portfolio assigns sprints that are in the past
Asked by Marianne Phinney:

I have a large portfolio plan with over a dozen teams and about 15 initiatives. I set custom sprints for each team because they each have their own sprint schedules and sprint names. I set them as fixed and included the start and end dates. I only included forward sprints from the time I set up the plan.

Now whenever the plan recalculates, some of the stories are assigned to sprints that are in the past, even when the status is in Backlog and they're not estimated. This makes the plan look much more optimistic than I should. I've been fixing those manually but it's a lot of tedium. Am I doing something wrong or is this a bug? Should I be deleting the custom sprints after they are closed?


Answers:
author: Martin Suntinger
body: Hi Marianne, JIRA Portfolio currently doesn't really know a concept of past/closed sprints, it just schedules from the start date of the plan. The start date is determined in the following way:

* If a plan update has been run, then the schedule starts from the last plan update date (Plan \> Update from date)
* If no update was done yet, but there is a release with a fixed start date, the schedule starts from the start date of the earliest release
* Otherwise the plan starts from today

Basically all sprints that are defined after the the schedule starts, are taken.

The intended process is to regularly run a plan update (Plan \> Update from date), e.g. after every sprint, or weekly. With that, you set a new start date for the plan, i.e., schedule whatever is remaining from the beginning of the next sprint or week. Fixed sprints that are before that date will then be ignored.

The alternative is to indeed just delete the custom sprints from the plan.


Tags: advanced-roadmaps

close

jira-software

schedule

sprint
I don't have the option to "Import Release" inside JIRA Portfolio.
Asked by John Lee:

For some reason, I don't get the "Import Release" button on my screen. My project has quite a few Versions already defined. Maybe I missed a step to correlate Versions to a Release?

NoImportRelease.png  
[](https://community.atlassian.com/t5/Advanced-planning-questions/I-don-t-have-the-option-to-quot-Import-Release-quot-inside-JIRA/qaq-p/380573?attachment-id=9374){#link_1160eb3084a196}  
[](/tnckb94959/attachments/tnckb94959/portfolio-for-jira-questions/246/1/NoImportRelease.png){#display_1160eb3084a196_0}


Answers:
author: Martin Suntinger
body: Hey John, this is interesting - there should not be any step you missed. Importing releases (which we use synonymously with the versions in JIRA) should work straight away after creating a plan.

Could this be an older version of JIRA Portfolio? (release import was introduced with Portfolio 1.8), also the latest release should show the button for CSV export. You can check the version via the help menu in the blue JIRA header next to the search, in the "About JIRA" dialog there should be a section on Portfolio as well.

If it is not an older version, I'd recommend opening a support ticket

image2015-7-28 9:35:50.png  
[](https://community.atlassian.com/t5/Advanced-planning-questions/I-don-t-have-the-option-to-quot-Import-Release-quot-inside-JIRA/qaq-p/380573?attachment-id=1969){#link_1160eb342533c5}  
[](/tnckb94959/attachments/tnckb94959/portfolio-for-jira-questions/247/1/image2015-7-28%209%3A35%3A50.png){#display_1160eb342533c5_0}

comments: author: John Lee
body: My version is 1.7.3. I don't have the option to upgrade to 1.8. I am on a trial version at the moment so I don't know if 1.8 is available with the trial. Also, my instance of JIRA is hosted locally so I don't know if that impacts what version we get


Tags: advanced-roadmaps
JIRA Portfolio - Initiative Issue Status not displaying
Asked by Eric:

Hey -

I'm working with JIRA portfolio and within the backlog view there is the "Issue Status" column which displays for some issues and not others.

image2015-7-23 8:45:46.png

We are creating Initiatives in JIRA agile and then linking them to portfolio. I really need to display the status so i can present a view to the my management team.

Do the issues need to be created in JIRA Portfolio for the Issue Status to be displayed there?


Answers:
author: Martin Suntinger
body: Hey Eric, As long as the initiative is linked to an actual JIRA issue (of any issue type, so you can create a custom issue type called Initiative, or link it to issues of any other type), the status should show up. Does the Issue link column column show an issue key for the initiative in Portfolio? If no, it would indicate there is no link to a JIRA issue established. If yes, I'd recommend to open a support case to investigate further.


Tags: advanced-roadmaps

issue

status
How does one enter historical data into Jira Portfolio?
Asked by Mark Hetherington:

I have my plan going forwards from the current spring onwards. The actual product development started 3 sprints ago and I am keen to enter these three historical sprints. I just tried the most recent sprint first.

I entered the custom spring for each team.

I then imported the relevant stories all of which were children of existing and current Epics. This showed these completed stories in each Epic without a Release, Team or Sprint allocated.

I then set the earliest start date for all the items in the current sprint to the first day of the current sprint to prevent them being allocated to the historical sprint that had capacity.

I then changed to current release to start from the beginning of the historical sprint.

For each completed story, I allocated the Release, Team and Sprint; this all seemed to work and the Backlog looked fine.

However, when I display the schedule, the completed stories allocated to the historical team sprints do not appear in the display. The historical sprints show nothing allocated and have full capacity.

I have tried all sorts of things to try and get Portfolio to recognise these items in the Schedules displays but with no success.

How can I get Portfolio to display the historical information correctly?


Answers:
author: Matthew Hunter
body: I replied on your support case, but I'll paste the response here in case anyone else stumbles across this question:
> JIRA Portfolio never displays historical stories in the schedule once backlog items are marked as complete. The graphical schedule is forward looking only, the backlog table is the only place that you can see those historical stories.
>
> We've got a feature request open that's similar to the request you're asking for, the ID is \[JPO-386\|<https://jira.atlassian.com/browse/JPO-386>\]. Please do vote on it, and if you can comment with your use case that will help our PMs when implementing the changes.


Tags: advanced-roadmaps
If estimate of Portfolio Plan has mapping with remaining estimate of linked issue, why do changing estimate value on plan updates remaining as well as original estimates of linked issue with estimates from Plan.
Asked by Radha Khullar:

.


Answers:
author: Martin Suntinger
body: The assumption is: As long as no plan updates have been made and there is no value for "Originally planned" set in JIRA Portfolio (you can see this column only when using the "Show completed issues" toggle), then we have a case of doing the initial planning, in which we're rather working with the initial (original) estimates, and what is remaining to be scheduled will be the same value, thus both of them are set to the same value on sync.

Once you've done a plan update, and the previous estimates are stored as "Originally planned", the sync with update only the remaining estimate field on the JIRA issues, and the value in the "orignally planned" column is synced to the original estimate.

In short: We assume during initial planning, we're rather estimating the original values, and original=remaining, later when updating, only the remaining is synced.


Tags: advanced-roadmaps
How to stop email notification while synching portfolio plan to linked Jira issues using bulk update from Apply updates to Project
Asked by Radha Khullar:


Answers:
author: Ryan Porter
body: I had this problem too, and I found that you can disable pretty much every kind of notification in the notification scheme in your project settings. I disabled notifications to watchers for any issue update and that pretty much solved my problem of having multiple people BEGGING me to stop spamming them with hundreds of useless notifications every time I triggered that option.

comments: author: Nathan Funk
body: But then they wouldn't get notifications for regular changes that they DO want to get notified about, no?


author: Stephen Sayler
body: It would be nice to have control over email notifications when saving Advanced Roadmaps changes to Jira, in the same way that's possible with Bulk Edit.

At times, the changes are important and worthy of notifying folks. Other times, I'm just doing cleanup resulting in dozens of notifications which is at best, unnecessary, and at worst, annoying.


author: Georgii Lumpov
body: [@Radha Khullar](/t5/user/viewprofilepage/user-id/544960)

Did you manage to have a solution to this?


Tags: advanced-roadmaps
Bug or Feature? Team member in more than one team doubles resource count
Asked by Barnaby Alderson:

We are currently evaluating the portfolio and have come across an issue where we assign a member to more than one team (they may have a required skill) and the effective member 'resource' count doubles automatically.

If say 2 epics are scheduled for the same release with the 2 separate teams, it will appear as if that member has double hours available per week without changing the availability in team (manual override) and the schedule is not accurate.

We know you can override it manually, but when scheduling across a larger number of projects and different 'multi-membership' people it becomes too error prone. To work around the problem we currently just use one team and assign to epics individually (not ideal). The schedule will always assign the user to the highest priority epic and won't overstate their resource count, etc.

So ideally when a member is in multiple teams it would work the same way and avoid the need to micro-manage the availability in a team to solve.

Is this a known problem or is some setting available to prevent the double up issue?


Answers:
author: Barnaby Alderson
body: Thanks Martin, good to see I'm not the first person to notice. Issue voted on and looking forward to a fix.


author: Martin Suntinger
body: Hi Barnaby, this is a known topic but has been a conscious design decision in a first step given the number of different usecases and variations we've seen related to this, thus we've started out with giving manual control over the availability in a team. There is an open suggestion ticket related to this: <https://jira.atlassian.com/browse/JPO-114> - please make sure to vote for it and comment on it if it does not cover everything.


Tags: advanced-roadmaps