[Jira.IssueAnalysis:]
Adds an Issue Analysis tab to the XLSX output document.
Macro Compatibility
The macro can be used in the highlighted input document types only. A greyed-out icon indicates not supported.
Usage
Does not work in Report Studio. The default columns output into the XLSX file are: 'Key', 'ParentIssueKey', 'Project', 'Priority', 'Reporter', 'Assignee', 'Status', 'Summary', 'Type', 'AffectsVersions', 'FixedInVersions', 'Environment', 'CreatedFull', 'CreatedHour', 'CreatedDay', 'CreatedMonth', 'CreatedYear', 'UpdatedFull', 'UpdatedHour', 'UpdatedDay', 'UpdatedMonth', 'UpdatedYear', 'Resolution', 'ResolvedFull', 'ResolvedHour', 'ResolvedDay', 'ResolvedMonth', 'ResolvedYear', 'DurationBucket' and 'Count'.
Parameter | Type | Deprecation Message | Preferred Parameter | Presence | Purpose | Options | Default |
---|---|---|---|---|---|---|---|
String | Mandatory | The JQL to execute. | N/A | N/A | |||
Boolean | Optional | Whether to add a chart to the Analytics worksheet. |
|
true | |||
Boolean | Optional | Whether to add a title to the Analytics worksheet. |
|
true | |||
List<String> | Deprecated | pivotTableColumnFields | The pivot table column fields. In Excel's PivotTable Fields UI, these correspond to the items in the 'Columns' section. You an use any of the heading names: 'Key', 'ParentIssueKey', 'Project', 'Priority', 'Reporter', 'Assignee', 'Status', 'Summary', 'Type', 'AffectsVersions', 'FixedInVersions', 'Environment', 'CreatedFull', 'CreatedHour', 'CreatedDay', 'CreatedMonth', 'CreatedYear', 'UpdatedFull', 'UpdatedHour', 'UpdatedDay', 'UpdatedMonth', 'UpdatedYear', 'Resolution', 'ResolvedFull', 'ResolvedHour', 'ResolvedDay', 'ResolvedMonth', 'ResolvedYear' and 'DurationBucket'. | N/A | N/A | ||
Boolean | Optional | Whether to add column grand totals to the pivot table. |
|
true | |||
String | Optional | Add a comment to make your document template more readable. The comment is discarded in the output document. | N/A | N/A | |||
String | Optional | The name of the Jira Connection | N/A | N/A | |||
Boolean | Optional | Should NCalc expression evaluation throw error on Overflow |
|
true | |||
String | Optional | The text to display should the macro fail to execute. Note that a poorly-specified macro (e.g. omitting mandatory parameters) will still result in an error message. | N/A | N/A | |||
List<String> | Deprecated | pivotTableFilterFields | The pivot table filter fields. In Excel's PivotTable Fields UI, these correspond to the items in the 'Filters' section. You an use any of the heading names: 'Key', 'ParentIssueKey', 'Project', 'Priority', 'Reporter', 'Assignee', 'Status', 'Summary', 'Type', 'AffectsVersions', 'FixedInVersions', 'Environment', 'CreatedFull', 'CreatedHour', 'CreatedDay', 'CreatedMonth', 'CreatedYear', 'UpdatedFull', 'UpdatedHour', 'UpdatedDay', 'UpdatedMonth', 'UpdatedYear', 'Resolution', 'ResolvedFull', 'ResolvedHour', 'ResolvedDay', 'ResolvedMonth', 'ResolvedYear' and 'DurationBucket'. | N/A | N/A | ||
String | Optional | The condition that must be true in order for the macro to be executed/evaluated. Must either evaluate to true or false, for example: "3+5=8" or "contains('abcd', 'z'). | N/A | true | |||
MacroMode | Optional | The mode in which variables are stored. In the legacy mode (default for Schedules), the variable created is a string and formatted. In the normal mode (default for Report Studio), the output variable is stored as a strongly-typed object, e.g. an Int32 or a List |
|
Legacy | |||
ObfuscationType | Optional | Obfuscation type. Use obfuscation to write reports where sensitive data is hidden. When used, ReportMagic guarantees that the same input string will map to the same output string for the whole of the report (but the next time the report runs, it will most likely map to a different value). If you use obfuscation, the property in your macro will not show up and instead, you will see a fake item of the obfuscation type chosen. |
|
None | |||
List<String> | Use instead of:
| Optional | The pivot table column fields. In Excel's PivotTable Fields UI, these correspond to the items in the 'Columns' section. You an use any of the heading names: 'Key', 'ParentIssueKey', 'Project', 'Priority', 'Reporter', 'Assignee', 'Status', 'Summary', 'Type', 'AffectsVersions', 'FixedInVersions', 'Environment', 'CreatedFull', 'CreatedHour', 'CreatedDay', 'CreatedMonth', 'CreatedYear', 'UpdatedFull', 'UpdatedHour', 'UpdatedDay', 'UpdatedMonth', 'UpdatedYear', 'Resolution', 'ResolvedFull', 'ResolvedHour', 'ResolvedDay', 'ResolvedMonth', 'ResolvedYear' and 'DurationBucket'. | N/A | N/A | ||
List<String> | Use instead of:
| Optional | The pivot table filter fields. In Excel's PivotTable Fields UI, these correspond to the items in the 'Filters' section. You an use any of the heading names: 'Key', 'ParentIssueKey', 'Project', 'Priority', 'Reporter', 'Assignee', 'Status', 'Summary', 'Type', 'AffectsVersions', 'FixedInVersions', 'Environment', 'CreatedFull', 'CreatedHour', 'CreatedDay', 'CreatedMonth', 'CreatedYear', 'UpdatedFull', 'UpdatedHour', 'UpdatedDay', 'UpdatedMonth', 'UpdatedYear', 'Resolution', 'ResolvedFull', 'ResolvedHour', 'ResolvedDay', 'ResolvedMonth', 'ResolvedYear' and 'DurationBucket'. | N/A | N/A | ||
List<String> | Use instead of:
| Optional | The pivot table row fields. In Excel's PivotTable Fields UI, these correspond to the items in the 'Rows' section. You an use any of the heading names: 'Key', 'ParentIssueKey', 'Project', 'Priority', 'Reporter', 'Assignee', 'Status', 'Summary', 'Type', 'AffectsVersions', 'FixedInVersions', 'Environment', 'CreatedFull', 'CreatedHour', 'CreatedDay', 'CreatedMonth', 'CreatedYear', 'UpdatedFull', 'UpdatedHour', 'UpdatedDay', 'UpdatedMonth', 'UpdatedYear', 'Resolution', 'ResolvedFull', 'ResolvedHour', 'ResolvedDay', 'ResolvedMonth', 'ResolvedYear' and 'DurationBucket'. | N/A | N/A | ||
List<String> | Use instead of:
| Optional | The pivot table value fields. In Excel's PivotTable Fields UI, these correspond to the items in the 'Values' section. For each column name, you can specify the aggregation to use via the ^ character e.g. column1^Sum. Omit this to use the default Count aggregation. Valid aggregation values are: 'Average', 'Count', 'CountNumbers', 'Max', 'Min', 'Product', 'StdDev', 'StdDevP', 'Sum', 'Var' or 'VarP'. For each column name, if and only if you have specified an aggregation, you can also specify the number format to use in the pivot table and chart. To do this, use an additional caret separator and specify the number format. For example: column1^Sum^0.00 would use 2 decimal places for the format. You an use any of the heading names: 'Key', 'ParentIssueKey', 'Project', 'Priority', 'Reporter', 'Assignee', 'Status', 'Summary', 'Type', 'AffectsVersions', 'FixedInVersions', 'Environment', 'CreatedFull', 'CreatedHour', 'CreatedDay', 'CreatedMonth', 'CreatedYear', 'UpdatedFull', 'UpdatedHour', 'UpdatedDay', 'UpdatedMonth', 'UpdatedYear', 'Resolution', 'ResolvedFull', 'ResolvedHour', 'ResolvedDay', 'ResolvedMonth', 'ResolvedYear' and 'DurationBucket'. | N/A | N/A | ||
List<String> | Deprecated | pivotTableRowFields | The pivot table row fields. In Excel's PivotTable Fields UI, these correspond to the items in the 'Rows' section. You an use any of the heading names: 'Key', 'ParentIssueKey', 'Project', 'Priority', 'Reporter', 'Assignee', 'Status', 'Summary', 'Type', 'AffectsVersions', 'FixedInVersions', 'Environment', 'CreatedFull', 'CreatedHour', 'CreatedDay', 'CreatedMonth', 'CreatedYear', 'UpdatedFull', 'UpdatedHour', 'UpdatedDay', 'UpdatedMonth', 'UpdatedYear', 'Resolution', 'ResolvedFull', 'ResolvedHour', 'ResolvedDay', 'ResolvedMonth', 'ResolvedYear' and 'DurationBucket'. | N/A | N/A | ||
Boolean | Optional | Whether to add row grand totals to the pivot table. |
|
false | |||
Int32 | Optional | The number of items to skip. | N/A | 0 | |||
Int32 | Optional | The number of items to take. |
|
1048576 | |||
List<String> | Deprecated | pivotTableValueFields | The pivot table value fields. In Excel's PivotTable Fields UI, these correspond to the items in the 'Values' section. For each column name, you can specify the aggregation to use via the ^ character e.g. column1^Sum. Omit this to use the default Count aggregation. Valid aggregation values are: 'Average', 'Count', 'CountNumbers', 'Max', 'Min', 'Product', 'StdDev', 'StdDevP', 'Sum', 'Var' or 'VarP'. For each column name, if and only if you have specified an aggregation, you can also specify the number format to use in the pivot table and chart. To do this, use an additional caret separator and specify the number format. For example: column1^Sum^0.00 would use 2 decimal places for the format. You an use any of the heading names: 'Key', 'ParentIssueKey', 'Project', 'Priority', 'Reporter', 'Assignee', 'Status', 'Summary', 'Type', 'AffectsVersions', 'FixedInVersions', 'Environment', 'CreatedFull', 'CreatedHour', 'CreatedDay', 'CreatedMonth', 'CreatedYear', 'UpdatedFull', 'UpdatedHour', 'UpdatedDay', 'UpdatedMonth', 'UpdatedYear', 'Resolution', 'ResolvedFull', 'ResolvedHour', 'ResolvedDay', 'ResolvedMonth', 'ResolvedYear' and 'DurationBucket'. | N/A | N/A | ||
String | Optional | If specified, adds a warning message for this macro. This is processed as an NCalc, and the warning message will ALWAYS be present and will be the value of the evaluated NCalc expression. | N/A | N/A | |||
String | Optional | The name to use for the analytics worksheet (which will contain the pivot table and chart). The data worksheet (which will contain the 'fact table') uses this name plus the suffix ' Data'. If a worksheet by this name already exists, the new name will have a number appended, e.g. Analytics1, Analytics2, etc. Excel does not allow blank names, names above 31 characters, and the following characters: :, /, \, ?, *, [, ]. | N/A | Issue Analytics |
Examples (2)
Example 1:
This example conducts the analysis on all matching issues according to the JQL:
[Jira.IssueAnalysis: jql=`project = "Magic Suite" AND created >= startOfMonth()]
Example 2:
This example conducts the analysis on all matching issues according to the JQL, and also customises and sets up the pivot table in the analysis worksheet:
[Jira.IssueAnalysis: jql=`project = "Magic Suite" AND created >= startOfMonth(), pivotTableColumnFields=Assignee, pivotTableFilterFields=Key, pivotTableRowFields=Resolution;Status, pivotTableValueFields=Reporter]