Issues  |  Knowledge Base

ALM Works

  • Products|
  • Download|
  • Pricing|
  • Support|
  • Company
ALM Works Business Continuity During the COVID-19 Outbreak
  • Structure
  • Structure helps Atlassian's largest customers track, manage, and visualize progress across Jira projects
    • Try It
  • Structure Overview
  • Atlassian Marketplace
  • Structure.Gantt
  • Add the power of Gantt charts to Jira projects
  • Structure.Gantt Overview
  • Atlassian Marketplace
  • Structure.Pages
  • The Ultimate Jira-Confluence Collaboration Tool
  • Structure.Pages Overview
  • Atlassian Marketplace
  • Structure.Testy
  • Test checklists extension for Structure
  • Structure.Testy Overview
  • Atlassian Marketplace
  • Colors for Jira
  • JQL-based color highlighting for enhanced issue navigation.
  • Client for Jira
  • Now an open source product!
    Interactive desktop client for Jira. Available via open source or as a free product.
  • Structure Version: 6.5.2 Feb 23, 2021
  • Free 30-Day Trial
  • Download Archive
  • Structure.Gantt Version: 2.7.1 Feb 16, 2021
  • Free 30-Day Trial
  • Download Archive
  • Structure.Pages Version: 1.6 Feb 1, 2021
  • Free 30-Day Trial
  • Download Archive
  • Structure.Testy Version: 2.5 Feb 3, 2020
  • Free 30-Day Trial
  • Download Archive
  • Colors for Jira
  • Version: 2.1.1 Sep 25, 2017
  • Free 30-Day Trial
  • Download Archive
  • Client for Jira
  • Version: 3.8.4 Aug 21, 2017
  • Free Version
  • Download Archive
  • Structure
  • Choose your platform:
  • Cloud Pricing
  • Server Pricing
  • Data Center Pricing
  • Structure.Gantt
  • Choose your platform:
  • Cloud Pricing
  • Server Pricing
  • Data Center Pricing
  • Structure.Pages
  • Choose your platform:
  • Server Pricing
  • Data Center Pricing
  • Colors for Jira
  • Choose your platform:
  • Server Pricing
  • Structure
    • Support Request
    • Documentation
    • Suggest an Idea
    • FAQ
    • Training
  • Structure.Gantt
    • Support Request
    • Documentation
    • Quick Start Guide
  • Structure.Pages
    • Support Request
    • Documentation
  • Structure.Testy
    • Support Request
    • Documentation
  • Colors for Jira
  • Support Request
  • Documentation
  • Client for Jira
  • Support Request
  • Documentation
  • FAQ
  • Knowledge Base
  • Contact support by e-mail
  • Support Description & SLA
  • About Us
  • Our Customers
  • Partners & Resellers
  • Contacts
  • Join Our Team!
  • News and Press Releases
  • Press Kit
  • Blog
  • Events
Call sales: +1 617 600 4369
  • info@almworks.com
  • sales@almworks.com
  • ALM Works, Inc.
  • 181 Wells Ave., Suite 204
    Newton, MA 02459
    USA
  • ALM Works Ltd.
  • Times Center, Suite 214
    Kantemirovskaya Str., 2A
    Saint Petersburg
    Russia 197342
  • Company
    • ALM Works Blog
    • Track Portfolio Plans in Real Time with Structure

Track Portfolio Plans in Real Time with Structure

By Robert Leitch on January 23, 2017

By popular demand Structure now integrates with Portfolio for JIRA – here's how to track your Portfolio plans with Structure for a complete real-time overview of everything that's going on.

As of version 3.4, Structure automation now supports Portfolio's Parent Link field, which means you can fully recreate Portfolio plans right inside Structure - great for tracking and collaboration purposes.

Once they're there, you can work with them using Structure's filters, transformations, link extenders and many other features. Structure will keep these plans synced with all changes pushed from Portfolio to JIRA, so you can be sure it's always up to date.

Here's how to easily track a Portfolio plan in real time using Structure's flexible progress calculation.

Plan in Portfolio, Track in Structure

As soon as you've configured your issue sources in Portfolio, you're ready to pull the same issues into a structure. To do this, we'll use the Inserters from Structure's automation tools.

Issue sources in Portfolio can be projects (in their entirety), saved filters and Agile boards.

This example assumes that all our Sub-tasks are assigned to Stories, and all Stories are assigned to Epics.

Step one - Pull Portfolio Issues Into Structure

First we need to get the issues that are in our Portfolio plan pulled into our structure. We'll start by pulling in Epics from projects and saved filters using a JQL Inserter.

Pulling in Epics from projects and saved filters

If our plan sources include projects and saved filters, we can address any number of them with a single JQL query in the format:

JQL query
project in ("project1", "project2", …) OR filter in ("filter1", "filter2", …)

We only need Epics at this stage (you'll see why in a moment) so we add AND issuetype = Epic to our query and we're all set:

Insert your project and filter Epics

Epics only, no Stories

Pulling in Epics from Agile boards

Next, we'll use an Agile Board Inserter to pull in issues from of the boards defined as issue sources for our plan. We're given the option to insert Epics or everything except Epics – we still only need Epics, so we choose the first option.

Insert your Agile board Epics

Epics only, no Stories

Now our structure should contain all the Epics from our Portfolio plan:

Portfolio plan Epics

It's not a big plan, but it's a plan

And we're ready to add the higher levels from our Portfolio hierarchy.

Step two - Recreate Portfolio Hierarchy

We add a Grouper to group our Epics by Parent Issue (defined by the Parent Link field in Portfolio):

Portfolio plan Epics

Be sure to add this grouper at the top (root) level of the structure

Now we have the top two levels (in this example, Initiative* > Epic) of our Portfolio plan hierarchy in Structure:

Portfolio plan Epics

Bonus - now you can move Epics between parent issues via drag-and-drop.

Next we add an Extender to put Stories under Epics:

Portfolio plan Stories

Nearly finished...

And another Extender to put Sub-tasks under Stories:

Portfolio plan Sub-tasks

All done!

Ready to Use

Our structure will be updated in real time as issues are edited in JIRA (or as changes are committed in Portfolio). It's important to remember that if issue sources change in Portfolio, they must be updated manually in Structure to keep everything in sync (for now, at least).

With our Portfolio plan in Structure, we can track important metrics such as remaining estimates, time spent and progress, all rolled up to the top level of the Portfolio hierarchy. We can quickly get totals across all our top-level issues simply by toggling Automation editing mode to expose the root-level structure element:

AggregatePortfolio progress

Quick way to see aggregate values for an entire structure

Structure has multiple options for calculating progress based on time tracking, status (where you can assign a percentage to every workflow status) or a custom percent field, with options for weighting aggregate values according to business value, story points and time estimates.

Next up - Track Multiple Portfolio Plans in Real Time.

*If you have more levels of hierarchy in your Portfolio, just keep adding Parent Link Groupers at the top level, making sure to check the 'Consider other groups' box (because effectively you'll be grouping groups).

Tags: Structure, Portfolio, tracking, real time, integration
Tweet
Structure

Hierarchical issues for great project management in Jira

JIRA Client

Desktop client for Jira

Structure plugin on the Atlassian Marketplace
Our Customers
  • logo
  • logo
  • logo
  • logo
Newsletter & Updates
Recent Tweets
Tweets by @almworks
Products
  • Deliver
  • Structure
  • Structure.Gantt
  • Structure.Pages
  • Structure.Testy
  • Colors for Jira
  • Client for Jira
  • Deskzilla
Resources
  • Documentation
  • Marketplace
  • Latest News
  • Blog
  • Support SLA
  • Legal
Company
  • About ALM Works
  • Customers
  • Contacts
  • Join our Team!
Quick Links
  • Customer Portal
  • Partner Portal
  • For Partners & Resellers
  • For Press
Site Map
Call Sales: +1 617 600 4369
info@almworks.com sales@almworks.com
Copyright © 2004-2021 ALM Works, Inc. All Rights Reserved.|Privacy Policy|Terms of Use