How is the Theme Report Calculated in Portfolio

This is the definition I found in the documentation:

Some key facts about themes:

-  Themes are a concept for labeling and tagging backlog (they are not time-oriented)
-  Themes are focused on relative resource allocation (i.e. how much are we spending on theme “X” vs. theme “Y”)
-  A story can be assigned to exactly one theme (if the stories in an epic are assigned multiple themes, then that epic and any parent initiative is assigned those same themes)

I'm confused w/ the definition.  If I'm using a Kanban board with Story Points, is the Estimate Pie chart based on Story Points across all the themes in the Todo column, and the Actual Pie chart based on Stories Points in the other columns (In Progress, Code Review, QA, and Done)?

What if I'm not using Story Points?  Is it based on time spent in each status?

Thanks!

 

 

 

2 answers

I have the same issue, Portfolio is very-very confusing!

I also don't know where can I find the 'Theme' label in Jira.

 

The Theme label doesn't exist in JIRA from what I found out.  It only lives in Portfolio so you cannot query for it from JIRA.  Maybe that will change later?

 

I also found out that the PIE chart is based on how you set your estimates to be (story points or time).  If you didn't set a default, any tickets in your plan will not be counted in the report, so it's probably good practice to set something by default (I set it to .5 or 1 points depending on the team).  The Actual PIE chart only aggregate tickets that have been completed (resolution != null), and Estimate PIE chart shows anything that has the Resolution ==null.

 

Hope this help.

Thanks Hoang! Since it's based on your estimates, this information can be misleading if teams your story points at different intervals. This assumes all teams are using consistent points which is only enforced within a SAFe model. It's possible the default estimate feature may need to be extended. 

If themes are not time based. Does that mean the Actual PIE chart contains all completed stories over all time, not just what is in a current sprint?  So that would mean there would need to be manual editing of the Plan to remove stories that have been closed for an extended time. I guess if a release is completed and removed from scope that could take those stories away from the themed report?

Bree Davies Atlassian Team Oct 12, 2017

Hi there, 

You can go back in time (beyond the current sprint) to include releases / issues which may have been closed in the Themes report. 

Just make sure you click on 'More' as per below:

Screen Shot 2017-10-13 at 5.14.34 PM.png

Then by choosing 'Scheduled Range' you can input your own date parameters if you select 'Specific Range'. You can choose the date range based on any of the other options available too. 

 

Screen Shot 2017-10-13 at 5.14.40 PM.pngHope this helps. 

Thanks,

Bree

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Wednesday in Jira

Join our webinar: How 1B+ feature flag events helped us build the new Jira

Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...

93 views 0 1
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you