Tracking progress and status

This page discusses the usage of Portfolio for Jira live plans (any version from 2.0 to 2.27). If you're using the redesigned planning interface, see the following pages instead:

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 for Jira can detect the estimation unit of these issues, with the following conditions to note:

  • If issues are estimated in hours or days, Portfolio for Jira will use time-based progress tracking.
  • If issues are estimated in story points, point-based aggregation will be used.
  • If you connect to boards and projects that have different plan units, Portfolio for Jira will let you choose the estimation unit to use when you're creating the plan.
  • If you leave your issues unestimated, progress will be calculated based on issue resolution, as well as the progress of child issues, if any.

Once your plan is created, a progress bar is displayed for individual issues. Parent issues will display an aggregated progress bar, corresponding to the individual progress of all the child issues. You can also check the progress of releases in the release view.

The progress tracking bar

The progress status bar shows the unestimated issues in relation to items that are estimated. This allows you to see the percentage of work done on estimated items as well as the issues that are still outstanding and require work.

  • Issue status: The actual workflow status of these issues
  • Progress: Sum of logged work on the linked Jira issues, as well as child issues, if any
  • When a parent issue is expanded, the bar shows the total progress of all the child issues.
  • Items with no progress are displayed as a faded grey line. 
  • Issues that are in progress show the completion percentage as a green line. 
  • Completed issues show a full green line.

  • If an uncompleted child issue is part of a completed parent, Portfolio for Jira will display a warning, indicating that the parent issue is already done — and therefore, the parent progress calculation won't take the children into account.

How to use the progress tracking

  1. Check out the progress tracking bar by selecting your plan > Scope and clicking the bar to see the details.
  2. Use the scope filters to sort by status, completion date, and schedule range.
  3. To see updated progress, make changes to the issues, and click Calculate.
    • For an estimated epic with child issues that are not estimated, when you set the epic to done, or log work time for the epic, the progress bar of the child issues will also be updated accordingly.
    • When a child issue is marked as completed, the progress bar of the the parent epic will reflect the progress, as well as the amount of completed points/time. You can also check the release progress by going to your plan > Releases.
  4. If an issue has multiple releases assigned, the progress of the releases depends on whether the the assignments were manual or automatic:
  • Manual assignments: The progress of issues contributes to the first release that's assigned to the issue.
  • Automatic assignments: The progress of issues contributes to the last assigned release.

Issues must meet the following conditions to be included and aggregated in Portfolio for Jira:

  • The status filter is set to open and completed.
  • Completed since filter is set to the desired timeframe.
  • The issue has a resolution date that's set.
  • Issue status is green. It is technically possible to have an issue status that is called "done", but is not in the green category.
  • Filter used as issue source includes completed issues. Filters behind boards usually contain completed issues, but if you're using a custom filter as a source for a plan, you'll have to verify that the completed issue shows up when you run the same query in Jira issue search.
  • Issue has a fixVersion set and it's part of a plan in Portfolio for Jira.

 Time based progress tracking

Time progress is measured by time logged on tickets and remaining estimates. When an issue is resolved, Portfolio for Jira displays it as completed, showing 100% progress. When work time is logged for an issue, its progress is calculated as follows:

Progress = Time spent / Time spent + Remaining estimate

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

When an issue is set to resolved, the bar will change to 100% complete.

Story point progress tracking

Story point progress is calculated from the estimates set in Jira issues. Portfolio for Jira considers an issue "Completed" when it is assigned to any status of the "Done" category, i.e. the green category. The progress of an epic is computed as:

Progress = ∑ [estimate (story 1) x progress (story 1)...estimate (story n) x progress (story n)] / estimate (epic)

If the issues are not estimated, progress is calculated based on the issue’s resolution field and the progress of child issues.

Calculating progress for issues with child issues

If an issue has child issues, progress is calculated as follows:

Progress = Number of resolved child issues / Total number of child issues

Calculating progress for issues without child issues

If an issue doesn't have child issues, and the issue is resolved (resolution field is not empty), the progress is 100%. Otherwise, the progress is 0%.

Issues without estimation

The following fallback is used if 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 estimates

If an issue has estimates, progress is calculated as follows:

Progress = Number of resolved child issues / Total number of child issues

Calculating progress for issues without estimates

If an issues doesn't have estimates, and the issue is resolved (resolution field is not empty), the progress is 100%. Otherwise, the progress is 0%.

Related topics

Last modified on May 23, 2019

Was this helpful?

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