Issues closed measure
eazyBI for Jira
By default Jira stores just issue resolution date (resolved issues are counted in Issues resolved measure) but not final issue closing date. But frequently it is important to analyze closed issues (which are in final closed status) and not just resolved issues.
For this purpose, when starting Jira data import in eazyBI plugin specify Closed statuses field value. By default standard Closed status will be selected but if you have custom workflows with different final closed statuses then specify one or several final closed statuses in this field. Or if you have next-gen projects selected for data import, make sure to list project-specific statuses as well; status value is a combination of status and project key, like "Done (DEMO)".
If closed statuses are specified then during Jira issues import issue status change log will be analyzed for closed issues (who are currently in one of closed statuses) and last workflow transition to closed status will be found to get issue closed date.
The following additional measures will be defined:
|Issues closed||Closed issues which are currently in closed status. On Time dimension grouped by issue closed date (last workflow transition date).|
|<custom number field> closed|
All custom number fields which are imported as measures will also have “… closed” measure created.
In addition following calculated measure will be defined:
|Issue closed date||If Issue dimension is placed on rows and expanded to detailed issues and Issue closed date is placed on columns then issue closed date for detailed issues will be shown.|
|Average closing days||Calculates the average closing days of closed issues (by issue closed dates on the Time dimension).|
Hidden Total closing days measure, that returns the total number of days from created to closed dates, is used in the formula.