I understand that story points resolved would be issues that have a resolution and resolution date, but how/why does this differ from story points closed?
The only difference I can see in my filters is that resolved has an issue that has the resolution rejected and closed does not include this...
Please help
Hi there !
In eazyBI, the difference between Story Points Resolved and Story Points Closed comes down to how issues are tracked based on resolution and status.
Story Points Resolved includes story points from issues that have a resolution (e.g., "Done," "Rejected," "Won't Do") and a resolution date, regardless of their current status.
Story Points Closed includes story points only from issues that have been transitioned to a "Closed" status category in Jira.
The key reason for discrepancies is that an issue can be resolved without being closed. For example, if an issue is marked as "Rejected," it will count toward Story Points Resolved but may not appear in Story Points Closed unless it is explicitly moved to a closed status. To align these metrics, check your workflow to ensure that all truly completed issues transition to a "Closed" status after resolution.
I currently have 3 statuses - rejected, descoped and done showing in resolved
In closed I have descoped and done... How can I treat descoped as rejected? and therefore excluded it from story points closed?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To exclude the Descoped status from your Story Points Closed calculation in eazyBI, you can adjust your measure by subtracting the story points associated with the Descoped status from the total Story Points Closed. Here's how you can modify your MDX formula:
[Measures].[Story Points closed]
-
(
[Measures].[Story Points closed],
[Status].[Descoped]
)
This formula calculates the total story points closed and then subtracts the story points of issues in the Descoped status, effectively excluding them from the total. This approach is recommended by eazyBI community experts for similar scenarios.
Alternatively, you can create a calculated member in the Status dimension that groups Descoped with Rejected. Then, adjust your measure to exclude this combined status group from the Story Points Closed calculation.
By implementing this adjustment, your Story Points Closed measure will exclude issues with the Descoped status, aligning with your reporting requirements.
I hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello!
Michael's solution is correct!
Just to add a bit more detail—Story Points closed refer to the current story points of issues in any of eazyBI’s closed statuses. These statuses can be configured in the eazyBI import options for the specific account:
https://docs.eazybi.com/eazybi/data-import/data-from-jira/issues-closed-measure
Best,
Ilze (eazyBI support team)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.