shafqat Atlassian Team

@Karine Manoukian Could you describe where this exclamation mark is showing? You can also try hovering over the exclamation mark and see if you get a tooltip saying why it's there. The exclamation mark can sometimes show if 2 people are editing the plan at the same time, and so we show a warning to refresh the page.

Hi @rahuldanwade, We were unable to reproduce this. Could you provide us with further info to help us reproduce this? It would be good to know the following: - Was PSR 1.0 part of the CPR 1.0 cross project release? - Was the story a child of the epic? - What version of Portfolio were you using? Thanks, Portfolio for Jira…

Hi @Daniel, One thing to note is that if your fixed release's start date is before today, then Portfolio will use today as the plan start. Only if the release start date is after today will the plan start from that release's start date. Could you verify if that is the case in your plan? Thanks, The Portfolio for Jira…

Hi Natasha, You could try applying the "Team" filter on your plan. It should be located to the right of the release filter. Let us know if that helps. Kind Regards, The Portfolio for Jira Team

Hi Mike, The best way to accomplish this would be to reduce your team's velocity by 10%. This would make your schedule take 10% longer. Let us know if this would work for you. Kind Regards, The Portfolio for Jira Team

Hi Timothy, There is an existing ticket for this: https://jira.atlassian.com/browse/JPOSERVER-210 We recommend voting on this issue and adding yourself as a watcher to be notified about updates. Kind Regards, The Portfolio for Jira Team

Hi Steve, New dependencies may not appear until the plan is calculated. Could you try re-calculating your plan and see if it causes your dependency to appear? If you're running Jira in Server, there was a bug causing issues to not appear that's been fixed in 2.11.0: https://jira.atlassian.com/browse/JPOSERVER-2069. So…

Hi TJ, The "Actual" column in the Themes report represents completed work. So only done issues will show up in it. If you wish to view the theme breakdown in your current sprint, you can apply the "Scheduling Range" filter from the "More" dropdown. Alternatively, you could apply the "Themes" filter to view all issues…

Hi Sergey, It sounds like it should work as you described. There could be a bug or a configuration issue causing this problem. Could you create a support ticket so that we may investigate this further: https://support.atlassian.com/contact/ Thanks, The Portfolio for Jira Team

Hi Michael, Typically all related stages should be part of a single story rather than 1 story per stage. The stages on a single story will be completed in order. Otherwise, separate stories are not ordered by their stages. Instead they will be scheduled like regular issues. So in your case, we would recommend having a…

Hi Rommel, Currently, it isn't possible to use script runner to automatically copy scheduled dates into target dates. However, there is functionality within Portfolio to do this. If you select all the issues in your plan, you can choose the "Set targets > Set target dates from calculated" operation to set target dates on…

Hi @Peter Andréasson, There is a ticket related to this on our tracker: https://jira.atlassian.com/browse/JPOSERVER-2009 I recommend watching and voting for this issue so that you are notified when it is fixed. Regards, Shafqat

Hi @Parag Thakkar, If you upgrade to 2.4.0 or above, you should get the team id properly, you can read more about that issue here: https://jira.atlassian.com/browse/JPOSERVER-1942 Cheers, The Portfolio Server Team

Hi Linnea, Have you set up Capabilities in your Hierarchy Configuration as mentioned here https://confluence.atlassian.com/display/JIRAPortfolioServer/Configuring+initiatives+and+other+hierarchy+levels ? Also, is the "Fix version" field visible on your Capability issue type? If it is not present, you may run into the…

Hi Marco, Currently, Portfolio doesn't expose which user made changes to a plan. However, we do have a suggestion for providing this kind of functionality: Cloud: https://jira.atlassian.com/browse/JPOCLOUD-382 Server: https://jira.atlassian.com/browse/JPOSERVER-382 Feel free to vote on these issues if they fit what you're…

Currently, descriptions can only be added to classic plans. Live plans currently don't support adding/editing descriptions. There is a suggestion for this: https://jira.atlassian.com/browse/JPO-1393. Please vote on this issue to highlight your interest on this feature. Thanks, Shafqat

This has been verified as a bug. You can follow updates on this issue here: https://jira.atlassian.com/browse/JPO-530

In the scope table, a white cell background indicates that the value was set by a user. Whereas a blue background means the scheduling algorithm calculated the value for that field. For example, if you set a team on a story, the team cell will turn white. The scheduling algorithm will not change this value when calculating…