What is a Portfolio plan
For Portfolio for Jira to capture the latest and greatest data from Jira, you'll need to organize your work in Jira, into what we call issue sources in Portfolio. Portfolio first captures your Jira issues, and uses the corresponding issue details to create the ideal schedule for your teams. The issues can be scheduled across sprints, months, even years.
These are the issue sources in Portfolio, into which you'll have to organize your work in Jira:
A project in Jira is a collection of issues that is defined according to your organization's requirements. For example, it could be a software development project, a marketing campaign, or a website enhancement request system.
Your board's filter is a Jira issue filter (a JQL query) that specifies which issues are included on your board. For example, your board may include issues from multiple projects, or from only one project, or from a particular component of a project. Only the administrator of a board or a user with the Portfolio for Jira administrator global permission can configure a board's filter.
Out of the three (3) issue sources, we recommend that you use boards — when boards are chosen, and it's a Scrum board in particular, Portfolio for Jira can then use the velocity of past sprints to determine team velocity. See Creating and deleting plans for more details.
What is a Portfolio plan?
A Portfolio plan is essentially a roadmap of all the work that you manage in Jira. Work can be anything you're involved in — it can be the issues your teams are working on, the releases your teams have committed to delivering, and more.
Portfolio pulls in these work items from Jira, and then uses an automatic scheduling mechanism to create a realistic schedule for your teams. This resulting schedule is based on relevant issue details that are logged in both Portfolio and Jira.
Over time, you may gain relevant knowledge on the work that your teams are doing. You'd typically know more than what the scheduling mechanism can determine — and more often than not, you'd know that a certain issue should be scheduled at a certain time, even if Portfolio schedules the issue differently.
Unfortunately, in the current Portfolio plans, it's not that easy going against the automatic scheduling mechanism. You can't simply drag and drop an issue to its ideal schedule — and this is one of the things we're changing in the new planning experience that's coming. To see what's specifically changing, see Overview.
This is how a Portfolio plan looks like, in the new experience:
Configure plan settings, like the name of your plan, or the issue sources your plan is using. You can also delete a plan from the settings icon.
Navigate to different views of your plan:
See Working with Portfolio plans to know more about these views in your plan.
Filter work in your plan, so you're viewing only the work you need to see. You can filter your work by projects, releases, teams, and other filters.
You can also choose to view only the issues that are scheduled for a certain timeframe in your plan:
See Filtering work for more details.
The different sections in the roadmap view of your plan, where you can view and work on issues accordingly:
See Working with Portfolio plans for more details.
Customize the view of the timeline, to make it easier for your audience to consume your plan. The following view settings are available:
See Viewing work for more information.
Perform actions for your plan:
As a best practice, make a habit of regularly reviewing and saving your changes in Jira. This way, you can inform stakeholders, keep the work items in Jira up to date, and ensure that your teams are ready to execute on your plan — all in real time.