Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How do you manage and visualize the differences between the original portfolio and the changes?

Maximilian Disselhoff
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!
July 22, 2026
I'm looking for advice on how to track and visualize changes in Jira Product Discovery between an originally planned portfolio value (baseline) and the current value over time.
At the beginning of the year, we define a target portfolio distribution (e.g., each innovation initiative contributes a certain percentage to the overall innovation portfolio). During the year, these values can change because initiatives are reprioritized, postponed, canceled, or their expected value changes.
Previously, we manually showed these changes in Confluence with indicators like 65% → 75%, but this no longer scales because values can be updated continuously in Jira Product Discovery.
My challenge is:
  • How can I preserve the original baseline value while still updating the current value?
  • How can I automatically calculate and display the delta/change between baseline and current values?
  • Are there native Jira Product Discovery features, best practices, automations, or reporting approaches for tracking these portfolio changes over time?
  • How do other teams handle portfolio baselines vs. current portfolio allocation in Jira Product Discovery?

Any recommendations or examples would be greatly appreciated. :)

1 answer

0 votes
James Gamble
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 22, 2026

Hola Maximilian,

I’d handle this with three separate number fields in Jira Product Discovery: Baseline allocation, Current allocation, and Delta. At the beginning of the planning period, populate the Baseline allocation field with the approved percentage, then treat that field as fixed. Continue updating only the current allocation as priorities and expected values change.

For Delta, create a custom formula that subtracts Baseline allocation from Current allocation. That would give you values such as +10 or -15 without needing to maintain the comparison manually in Confluence. You can also create a second formula for percentage change if that’s useful, although you’ll need to account for a baseline of zero.

Jira Product Discovery’s formula fields are described here.

A list view is probably the clearest native presentation because you can place Baseline, Current, and Delta side by side, then filter or sort by the largest changes. A matrix view could also help compare the current value against another dimension, but it won’t provide a historical trend line on its own.

The important limitation is that Jira Product Discovery doesn’t provide true portfolio baselining or time-series reporting for arbitrary field values. The work item history will show that a value changed, but it won’t automatically turn those changes into a chart showing the portfolio at each point in time.

If the baseline should be captured automatically, you could use an automation rule triggered by a status change, such as Approved or Baseline Set. The rule would copy the current allocation into the baseline allocation only when the baseline field is empty. That prevents later changes to the current allocation from overwriting the original plan.

For snapshots across the whole portfolio, I’d use a scheduled export to Google Sheets, Excel, a BI tool, or Atlassian Analytics if it’s available in your environment. Each export should include a snapshot date, idea key, baseline, current value, Delta, status, and portfolio category. That gives you the historical trend reporting that JPD’s native views don’t currently provide.

Thanks,

James

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events