This conversation was replied to privately by the support team.
Message below:
1. Story point “burn down” when it reaches X statuses (in progress, not Done statuses).
Instead of Story Points resolved in the burndown, you may count Story Points in the burned-down statues at the end of each day during the sprint.
To do that, please create a calculated member in the Transition Status dimension to aggregate all the statuses you consider as burned down. Then create a new calculated measure that uses aggregated statuses with the Story Points History measure in a tuple.
Example of calculated member in Transition status dimension:
Aggregate( { [Transition Status].[depending build - staging], [Transition Status].[qa fail], [Transition Status].[developer testing - staging], ...etc } )
Please add all the needed statuses and use the correct status names. Please, read more about Aggregate here: Aggregate
Then create a measure (in Measures) using aggregated members and measure Story Points history. Use this measure instead of Story Points resolved:
( [Measures].[Story Points history], [Transition Status].[Burned statuses] )
And about tuple, here: Tuple
- About Average Story size per Sprint .
For example, you can use measure Story Points Resolved with hidden measure Issues with Story Points Resolved to calculate the average. You can read more about hidden measures here: Jira custom fields
To calculate the average, consider creating a new calculated measure with the formula::
CASE WHEN [Measures].[Issues with Story Points resolved] > 0 THEN [Measures].[Story Points resolved] / [Measures].[Issues with Story Points resolved] END
You can use Sprint dimension into rows together with this calculated measure.
- The Ratio of Ticket Types per sprint .
You may use Pie chart to show this information: Create charts
Please choose the Issue Type dimension in the rows and dimension Sprints in Pages to select the sprint. If you want to see all the sprints, then add the sprint dimension to the columns. Depending on how you want to see the ratio - for committed issues or issues closing, choose one of the Sprint Scoupe measures: Sprint issues committed, Sprint issues completed, etc. Please read more about Sprint scope measures here: Jira Software custom fields
For example, Sprint issues at closing in sprint HERB Sprint 3 are in the picture below:

Is this something you are looking for?
-
Effort level per story point.
If not using Time tracking, we have predefined measures called “Average resolution days” and “Story Points resolved”, consider using those. Read more about Story point measures here: Jira Software custom fields
Consider creating a new calculated measure with the formula:
CASE WHEN [Measures].[Story Points resolved] > 0 THEN [Measures].[Average resolution days]/ [Measures].[Story Points resolved] END
See the example with Effort level by sprints below:

Kindly,
Ilze