Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Portfolio for Jira: Share your tips!

Josh Frank
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 1, 2017

The Portfolio for Jira team wants to hear from you. Share your top tips for building a great Portfolio for Jira plan for a chance to win some Atlassian swag. 

Do you structure your teams in a certain way?  Do you take a unique approach to estimating? What’s your approach to using releases? Do you take advantage of a particular report? Share your thoughts with the Atlassian community!


Cameron Eldridge December 15, 2017

I'm trying to submit a post with wiki formatting, but it keeps disappearing.

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 15, 2017

They're going into spam.

One of the spam filters is "was the same text posted very recently", so once your first post is filtered, attempts to re-post it are pretty much automatically filtered too.

Anyway, I have yoinked the last one out of spam, it should stay now!

Cameron Eldridge December 15, 2017

You rock. Thanks, Nic!

Like Nic Brough -Adaptavist- likes this
Cameron Eldridge December 15, 2017


  • Make it a habit of clicking the Calculate button every time you navigate back to your plan. Data may have changed while you were away.
  • Create a page template in your Confluence space to capture requirements for each Initiative. This will help ensure everyone has a good grasp on the scope of these big work items.
    • You can link these directly to your Jira issues.
  • Create an Initiative kanban board to track the progress of high level Portfolio items.
    • You can also create an Epic kanban board to show which Initiative each Epic is linked to.
    • Include the Parent Link field on the board's Card Layout to easily see parent Initiatives.

Committing Plan Changes

  • Try not to leave an abundance of uncommitted changes in your plan. Hundreds of uncommitted changes can make it difficult to remember everything you adjusted if you haven't visited your plan in a couple of days.
  • Ensure changes made in one scenario don't overlap with changes in another scenario. Otherwise, you may end up with conflicts that prevent you from committing changes.

Issues sources

  • Scrum teams should use boards as their issue sources to take advantage of their sprints and associated history.
    • Portfolio can calculate a suggested velocity for each scrum team based on the story points completed in previous sprints.
  • When using a single issue source in a plan with multiple teams, Portfolio often schedules work for the "incorrect" team. This is especially prevalent when teams don't have any members assigned to them.
    • Leverage the Portfolio Team field in your issues to avoid scheduling conflicts.
      • Share your plan's private teams so that you can designate them in Jira issues.
        • Of course, you'll need to add the Team field to all applicable issue screens.
      • Alleviate scheduling conflicts even further by creating a unique issue source for each team in your plan.

Multiple Scenario Planning

  • Create at least two scenarios for your plan.
    • Ensure that one of them, such as "Live," always reflects your Jira data in its current state.
  • Title your scenarios based on their purpose.
    • Examples
      • Live
      • Sandbox
      • Grooming
      • Best Case
      • Release Shift

Plan Permissions

  • Avoid giving too many users edit permissions of your plan. Committing changes back to Jira can be very dangerous.


  • Apply default estimates to unestimated work items to get them to show up on the timeline.
    • This is most helpful when used in Epics and Initiatives that don't contain any child issues.
  • Pay attention to the ranking of stories in your Backlog. Rank holds the most weight in Portfolio's scheduling algorithm.
    • Estimated issues not assigned to sprints will automatically be placed in fake, placeholder sprints (e.g. Sprint 1, Sprint 2, etc.) that only exist in Portfolio, especially when ranked low in the backlog.
      • As a result, the plan may appear to be overbooked. Re-rank those issues higher in the backlog, then assign them to a sprint if the overbooked schedule doesn't revert back to green.
      • If the schedule is still red, overbooking may be present elsewhere in the plan.

Leveraging Target Dates

  • Target Dates are an easy way to place ideas on the timeline. This works for unestimated items that are not assigned to a release.
    • First, ensure you have your plan configured to base unestimated item scheduling on target dates.
    • Then, use the cogwheel icon in the Scope view to expose these fields for modification.
      • Remember to click Calculate to see your changes reflected on the timeline.
    • The Target start and Target end date fields can be illustrated directly in Jira issues as of the Portfolio 2.8.0 release.

Re-prioritizing work items

  • Portfolio's drag-and-drop ranking functionality is best used for bigger items in the hierarchy, e.g. Epics and Initiatives, since Portfolio only allows you to rank one item at a time.
    • If you need to re-prioritize multiple issues at the story level, rank them in your team's board(s) instead of Portfolio.
      • Clicking the Calculate button in Portfolio will cause the plan to sync with Jira.
        • The changes you make in your project(s)/board(s) will be reflected in the associated plan.

Stages and Skills

  • Stages and Skills are very advanced features of Portfolio. Do not worry about using these when you're getting started.
    • Applying stages and skills will drastically increase the amount of manual maintenance you'll need to do in your plan.

Working hours and days

  • Don't forget to add company holidays to automatically account for reduced capacity during those times.

Using the timeline

  • Remember that the timeline and scope views can be different for each user; they are not configured globally for a plan.
  • Configure the timeline and scope settings using the two cogwheel icons in the Scope view.

Configuring teams

  • Be sure to associate teams with an issue source. Not doing so can cause various scheduling errors and prevent work from showing on the timeline entirely.

Creating and managing releases

  • When you need to create releases in multiple projects that are already part of your plan, create the releases in Portfolio.
    • You can set the release dates and group them together into cross-project releases.
  • Ensure that sprint end dates align with release end dates. Sprints that end even one day after a release will cause the timeline to turn red.
    • This can be a misleading representation of being overbooked.

Excluding releases from your plan

  • Be careful when excluding releases from your plan because the issues tied to those releases will also be excluded.

Using the later release

  • The Later release lets you take advantage of Portfolio's scheduling algorithm. As long as you rank your work and have estimates (time or story points), you don't need to use releases at all!

Sharing Reports

  • Configure your view before sharing your report. When providing a link to users or embedding the report in a Confluence page, users will see your configured view.
  • Embed reports in Confluence using the report's iframe link within an HTML macro.
    • Customize the size of the iframe by adjusting the width and height parameters.
      • Setting the width to 100% will cause the iframe to span the entire width of the section in which it is embedded. 

Themes Report

  • Consider correlating the colors your Epics with your Themes to easily identify theme-related work outside of Portfolio.
    • Publish a color guide in Confluence for users and stakeholders to reference.
    • Epic colors are easily managed in the Backlog of a Scrum board.
Like # people like this
Josh Frank
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 21, 2017

@Cameron Eldridge, These are fantastic tips. A huge thank you for taking the time to share! 

Like Cameron Eldridge likes this
Cameron Eldridge December 22, 2017

@Josh Frank, you’re welcome!

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 27, 2018

Wonderful information :)

Like Cameron Eldridge likes this
JulienFritsch July 5, 2018

Excellent !! @Cameron Eldridge, how would you sort this problem? Sorry to ask directly, but I doubt that any new user can help and you look to have so much experience, that I believe it's a case that you might have faced.

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 19, 2019

@Cameron Eldridge how do i go about creating "Initiative Kanban board" in JIRA?

Cameron Eldridge November 20, 2019

Hi @amitamorakhia


Here are some instructions to create and configure an Initiative Kanban board.



1. Select Boards > View All Boards from the top navigation bar.

2. Click Create board at the top-right of the page, and choose to create a Kanban board.

3. Click Create a Kanban board, then choose to base your board on an existing project.

4. Follow the prompts to set up your board. Your Kanban board will have a default filter. Modify the query as shown below. XYZ will be the key of your selected project.

project = XYZ AND issuetype = Initiative ORDER BY Rank ASC

5. Congratulations — you have created a new board! Now it's time to configure your board.



1. Navigate to the board's Card Layout tab via Board > Configure > Card Layout.

2. Add the Fix Version/s field to display the release your Initiative is planned for. If you use Portfolio 3.x, you may also want to add the Target start and Target end fields. Alternatively, include meaningful custom fields you leverage in your instance for Initiatives.



1. Be sure to configure your board columns relative to your Initiative workflow statuses.

2. Configure your Issue Detail View so that you have quick visibility into pertinent fields.

3. Add Quick Filters to narrow your board results. For example, add a "Current Release" quick filter to see Initiatives in your next planned release. Include your project key (XYZ) to speed up the query.

fixVersion = earliestUnreleasedVersion(XYZ)




Like amitamorakhia likes this
kovame01 March 29, 2019

@Cameron Eldridge Can you elaborate on the following:  

Multiple Scenario Planning

  • Create at least two scenarios for your plan.
    • Ensure that one of them, such as "Live," always reflects your Jira data in its current state.
  • Title your scenarios based on their purpose.
    • Examples
      • Live
      • Sandbox
      • Grooming
      • Best Case
      • Release Shift

I am particulary interested in the Release Shift scenario.  Assuming this allows you to take a baseline of your plan and then the ability to see changes in the Live view of the plan and how they differ from the baseline ??

Cameron Eldridge March 29, 2019

Hi @kovame01,


The data flowing into Portfolio is dynamic, so there's no way to snapshot data within live plans. Release Shift could be used to assign issues to earlier or later releases, re-rank them, and calculate the changes to see shifts in the Schedule (timeline) view.


You could also swap to the Target schedule view if you've previously set Target start and Target end dates to compare against the shifted release dates.


Portfolio for Jira - Release Shift.png




Log in or Sign up to comment
AUG Leaders

Atlassian Community Events