Roi Fine Atlassian Team

Hi Traci, Getting all child issues of an initiative via JQL is possible since Portfolio 2.10, you can check the details here: https://confluence.atlassian.com/jiraportfolio/portfolio-for-jira-2-10-release-notes-940678731.html#PortfolioforJira2.10releasenotes-childissues Cheers,

A description to the doc that describes the plan limitations can be found here: https://confluence.atlassian.com/jiraportfolioserver/creating-and-deleting-plans-802170502.html

You assumed correctly, there is a feature suggestion ticket you can follow or comment on here: https://jira.atlassian.com/browse/JPOSERVER-35?src=confmacro And get notified once this feature is available. Cheers,

Hi @Daljit Singh, there is a filter under "More" (next to the search box) which you can use and set to "Open & completed" - the default filter setting is "Only open issues" which is why completed issues don't show up. Hope this helps! Cheers, Roi

Hey Patrick, There is another way to create tickets in your Portfolio scope table, If you hover for 1-2 seconds on the line between 2 issues you will have an option to create issues without the need to go to the bottom of the table. Check "option 2" in this…

Putting aside dependencies and other external date factors such as releases, Portfolio's algo takes into account rank as the main factor for scheduling. I think your direction is good, there is a lot of trial and error in the scope section but after a few times the theme report should show your desired outcome. I hope that…

Hi Kevin, You can actually filter the scope table by themes. In the filters bar, select "more" than you will see a dropdown selection of 4 more filters, one of them is themes. I hope it will do the trick. Cheers,

Hi Qais, You can think of a Portfolio plan as a large container for issues from multiple boards or projects that you wish to plan and track progress of. If your organization has multiple roadmaps(different products/work streams) I would recommend to create multiple plans. We recently introduced a new feature called…

Hi Alessandro, We released a fix for it on version 2.6.1 Please update for the new version to enjoy the full functionality of Programs. I hope that helps, Cheers!

Hi Angela, It really depends on your orgnazation needs and way of work. A good tip I can share is to try and think which project structure will have the least cross project dependcies. There are quiet a lot community conversations about the matter that worth a check:…

Hi Angela, You are right, to use cross project intiatives you will need to create a new project for intiatives. See instructions in the second paragraph of this page: https://confluence.atlassian.com/jiraportfoliocloud/configuring-initiatives-and-other-hierarchy-levels-828785179.html The good thing about having a dedicated…

Hi Robert, You will need your Confluence admin to enable the HTML macro since it is disabled by default. Check the confluence docs here: https://confluence.atlassian.com/conf54/confluence-administrator-s-guide/managing-add-ons-and-macros/enabling-and-configuring-macros/enabling-html-macros Please be aware that enabling the…

Hi Rita, Above the schedule, in the filters menu, you can find a search box. If you write the name of the initiative you will view only the issues linked to that initiative. I hope that helps! Cheers,

Is this request comes from a need to restrict the input for the team field?

Hi James, The Portfolio Team field, when surfaced in JIRA, only populates the shared teams(configured in Portfolio). Currently there is no option to restrict certain teams from certain projects. Can you shed some more light on what are you tring to do and why? Cheers, The Portfolio for JIRA team

Hi Mark, Releases are Portfolio's refrence for time. You can use releases as milestones or quarters if you wish to view a time refrence on your schdule reports. I hope that helps,

Hi Carlos, In Portfolio there is no assignee field but a "member" field. You can add it to your scope table to view it and assign a member to a task or let Portfolio automatically assign it. The default issue level to be assigned by Portfolio is sub-task. If you wish Portfolio to assign higher level hierarchy items such as…

Hi Carlos, Unfortunately you can't surface Target start and end fields in the JIRA issue screens. These fields are mostly intended to assist Portfolio users in roughly estimate and baseline the work on an issue inside Portfolio. You can always create a suggestion in https://jira.atlassian.com and the team will consider if…

Hi Matthias, We call what you call a theme, an initiative but essentially it does not matter as both represent a work item with higher hierarchy than an epic. Answering your question, there is no way to link a story to a higher level work item other than epics. That means you can't "jump over" an hierarchy level. I.e: a…