Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

KPI reporting in EazyBI - To arrive it First time UAT pass rate %

Currently JIRA is setup in below fashion

Scenario 1: 

1. Story will have 2 sub tasks the moment it is moved from Ready for UAT to IN UAT status.

2. one sub task for preparer to approve another one for reviewer to approve

any one rejects the story will turn to UAT rejected.

In such a scenarios how do i go about measuring following KPI - First time UAT pass rate %

Scenario 2: 

Now when the developer fixes the issues he mentions that it require a product fix before he can fix the issue from his end. in such a situation how do i measure the following KPI - Bug fixes percentage due to product feature unavailability/temporary issue

kindly help



1 answer

1 vote

Hi @satish v 

I can provide an example for the first scenario. I just want to point out that the second scenario is unclear to me. If possible, please provide more details on how the developer "mentions that it require a product fix" and how you expect to calculate the KPI?

As promised, the suggestions for the first scenario - eazyBI can analyze issue history, and with that, issue transitions through statuses. The KPI "First time UAT pass rate %" should consider the total number of issues transitioned from "IN UAT" to "UAT pass" and the ones that did it on the first try - the only transitions from "IN UAT" is to "UAT pass".

The total number of issues is a tuple of the measure "Transitions to status issues count" and the Transition dimension member "IN UAT => UAT pass". The formula could look similar to the one below:

([Measures].[Transitions to status issues count],
[Transition].[IN UAT => UAT pass])

The second part, considering issues transitioning the first time around, is more complex, as it has to look at each particular issue. See the suggested formula below:

-- iterate through issues
-- filter issues with a transition date from the status
Not IsEmpty((
[Measures].[Transition from status first date],
[Transition Status].[IN UAT],
-- only one transition from status
([Measures].[Transitions from status],
[Transition Status].[IN UAT],
[Time].CurrentHierarchy.DefaultMember) = 1
-- and the transition is to UAT pass
([Measures].[Transitions to status],
[Transition].[IN UAT => UAT pass],
[Time].CurrentHierarchy.DefaultMember) > 0
),([Measures].[Transitions from status issues count],[Transition].[IN UAT => UAT pass])

Now you can divide the number of issues transitioned the first time around, with the total number of issues in a separate calculated measure.

Please look at the eazyBI documentation page for more information on defining calculated measures -​


Roberts //

Hi @Roberts Čāčus Thanks for the 1st scenario example, it helped me to create a report. I'll detail the second scenario,

We have a checklist field called "Reason" and it has two option relates to product,

  • Product fix
  • Product feature
  • Others

Developer will mark this field option if it relates to product and transition to "Blocked" status.

We need to calculate the KPI(%) based on "Reason" field value(product related and non-related) with total number of issue transitioning from "Blocked" to "Ready for UAT" status.

Hope the requirement is clear. Appreciate your help on this Roberts.

Hi @Prakash


eazyBI can import checklist fields as dimensions. However, as these fields are multi-value, eazyBI can't analyze their historical values. Thus, the data will be related to the field's current value.

You can look at the example from the first scenario for the total number of issues transitioning from "Blocked" to "Ready for UAT" status. To determine the issues that transitioned through a specific transition and has a value in the field, include the dimension and its specific value. The KPI formula could look similar to the one below:

([Measures].[Transitions to status issues count],
[Transition].[Blocked => Ready for UAT]) > 0
([Measures].[Transitions to status issues count],
[Transition].[Blocked => Ready for UAT],
[Reason].[Product fix])
([Measures].[Transitions to status issues count],
[Transition].[Blocked => Ready for UAT])

If you need to include more than one reason, create a new calculated member in the Reason dimension, aggregating the desired members. See an example for the Priority dimension on our documentation page -



Roberts //

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events