Tracking status and progress of issues

You can track the progress of issues in your Jira application directly from your plan in Portfolio for Jira.

  • When you connect a plan with your boards and projects, Portfolio will detect the estimation unit they have.
  • If you estimate your issues in story points, point-based aggregation applies. 
  • If you connect to boards and projects that have different plan units, Portfolio lets you choose the estimation unit during plan creation.
  • If you leave your issues unestimated, progress is calculated based on the issue’s Resolution field and the progress of child issues.

How to track the status of issues in Portfolio

Portfolio can show the up-to-date status of issues as they move through their Jira workflow.

Example:

A developer moves an issue from To Do to In Progress.

 

Portfolio reflects the change in the Issue Status column displayed in the scope table.

Before

After

Track status of issues in the Schedule

You can see the status of your Jira issues in the schedule by hovering over the name of the issues. Once you hover over an issue, a card will pop up showing the issue status.

The Schedule is a realistic forward-looking visualization of work that has to be done. For this reason, when an issue reaches the Done status, it won't be visible in the Schedule anymore. You can still see your completed issues from the current sprint by following these steps:

  1. Go to Scope > More > choose Status.
  2.  In the filter dropdown choose Open and completed issues.
  3. The Completion date filter has a timeframe set. Go to More > choose Completion date and define a timeframe.



  4. Make sure your issues in Jira have a value set for the Fix Version field.
  5. If you're using a filter as an issue source to pull issues into your plan, make sure the filter includes completed issues.

An epic displays the status "In Progress" as soon as one of its child stories starts. The status will change to Done once all the child stories are completed.

Track status of issues in the scope table

See the status of Jira issues in your scope table by going to Scope > and check Issue Status.

A new column appears with the different statuses.

Note

To see completed issues ensure that your Jira board has a Done column mapped to the green Done status, and all completed issues have been moved to this column. Learn how to configure columns and how to map statuses.

How to track the progress of issues in Portfolio

Portfolio uses the status and estimate of the issue to track and visualize progress. You can still track progress, though, if the issues don't have estimates. Learn more about issues without estimates in How Portfolio uses estimates to track progress.

The issue progress is visualized by the progress bar. It can be added to the scope table by following these steps:

  1. Go to Scope > and check Progress.
  2. The Progress column displays a bar that will be either grey for not done or green for done. Click on the issue progress bar to see a card with detailed progress information as shown in the example below:

  3. In order to see the updated progress, change the issue's status and click Calculate.

Progress tracking bar

The progress bar represents the sum of time logged on the linked Jira parent issues, as well as their child issues. 

  • Completed issues show a full green line.
  • Issues with no progress are displayed as a grey line.  
  • Progress of a parent issue is based off progress of its child issues. For example, an epic has 5 stories and each one has an estimation of 1 story point. If 3 stories have been completed, the epic's green progress bar will be at 60%.
  • Stories in progress show the completion percentage as a green line.
  • If an open child issue is part of a completed parent, Portfolio shows a warning saying that the parent issue is already done. The parent progress calculation won't take the children into account.

Some things to note:

    • When you set an epic that has an estimate as Done, but its children don't have estimates, the children progress bar won't show up as completed.



    • When a child issue is marked as completed, the epic progress bar will show progress and the amount of completed points/time.  You can also check the issue progress by going to your plan > Releases.

      • Completed - Points completed out of the original estimate.
      • RemainingRemaining points to completion.
      • Total issues - Total number of child issues.
      • Unestimated - Number of unestimated issues.

To see completed issues in your scope table, ensure you meet the following requirements:

  • Your Jira board has a Done column mapped to the green Done status, and all completed issues have been moved to this column. Learn how to configure your Jira workflows here.
  • The Done column on your Jira board has a resolution of Done set on it.

    Learn how to set the resolution.

    Go to Jira > choose your project > Active sprints > Columns > Check Set resolution.

    Learn more about your boards configuration here.

  • The Status filter is set to "Open and completed issues".

    Learn how to set the filter.
    1. Go to scope > More > choose Status > in the filter dropdown choose Open and completed issues.






  • The Completion date filter is set to the desired timeframe.

    Learn how to set the filter.
    1. Go to scope > More > choose Status > in the filter dropdown choose Open and completed issues.
    2. The "Completion date" filter has a timeframe set. Go to More > choose Completion date and define a timeframe.



  • Issues in Jira have the Fix Versions field set.

  • If you're using a filter to bring issues into your plan, make sure the filter includes completed issues.

How Portfolio uses estimates to track progress

Portfolio uses the status and estimation value of issues to track and visualize progress. If the issues from the Jira board, project, or filter you connected have estimates, these estimates will be imported with the issues themselves to the plan and used.

In the following example, you can see how estimates interact with progress. The epic IOS-1 has 4 stories with each story having estimation of 1 story point. If 3 stories have been moved through the Jira workflow to the Done board column (they're now completed), the epic's green progress bar will be at 75%.

See the progress details by clicking the bar.


Issue estimates can be assigned to issues in multiple ways:

  • Imported from Jira - If the issues from the Jira board, project, or filter connected to your plan have estimates, these estimates will be imported into the plan.
  • Manually assigned in your scope table - Learn more about the scope table here.
  • Default estimates - Learn more about default estimates here.

If issues don't have any estimate assigned, progress can still be tracked based on Status and Resolution. Statuses represent the position of an issue in the workflow. A status can be mapped to one workflow step. Resolutions are the ways in which an issue can be closed. Learn more about status and resolutions here.

Estimated issues progress tracking

In this section, you'll learn about the different ways Portfolio tracks progress depending on the estimation type you're using.

If issues are estimated in hours or days:

If Time tracking is switched on in Jira, Portfolio will use it to track progress.
Time progress is measured by time logged on tickets and remaining estimates. When an issue is resolved, Portfolio displays it as completed, showing 100% progress.

If no remaining effort is set, the original estimate is considered and the progress is aggregated up the hierarchy.

If issues are estimated in story points:

Story point progress is calculated from the story point-based estimates that are set in the Jira issues. Portfolio considers an issue completed when it's assigned to any status of the Done category.

When your issues have no estimation, progress is calculated based on the issue’s Resolution field and the progress of child issues.

  • Calculating progress for issues with child issues:
    The progress of a parent issue such as an epic, is calculated from the number of resolved child issues.

  • Calculating progress for issues without child issues:
    If an issues doesn't have child issues, the progress will display either 100% or 0% completion, but won't show partial progress.

If issues come from multiple Jira issue sources with differing estimation types:
If an issue is included from multiple issue sources, Portfolio picks the conversion factor from the first issue source saved in the database. You can choose your estimation type during the plan creation process, and define an estimate method conversion factor by following these steps.

Unestimated issue progress tracking

When an issue doesn't have an estimate but has been resolved, the progress is marked as 100%. If an issue doesn't have estimates and it hasn't been resolved, the progress is marked as 0%.

Learn how to add default estimates to your unestimated issues by following these steps.

Tracking progress of releases

Progress information is based on a static snapshot of issue statuses, estimates, and logged time, and release progress is calculated from the progress of the issues in the release.

Example:

In the following example, we have an epic that has 100 story points worth of work. The epic and its stories are assigned to a release called "iOS beta," and two stories worth a combined 50 story points have been completed.

In the following image, 50% of the release has been completed. 

Learn more about releases here.

Last modified on Mar 21, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.