Reports
Did you know that you can generate reports based on created events in Calendar?
To switch from Calendar mode to Reports mode, click the Reports mode button, located on the top right corner of the screen.
|
You'll be presented by the screen below. Depending on the type of report you want to use, go to either Predefined reports, Report or Pivot report tab.
 |
For further instructions on how to configure and generate reports, please refer to the Predefined reports, Standard report and Pivot report pages.
Users can also create Report templates to save various report configurations and easily apply them in the future to any calendar(s) of their choice. Please refer to the Report templates page
To distinguish the empty values shown as a dash symbol in generated reports.
Now, when a user hovers over a “-” sign, one of the following tooltips appear:
“Not set” is shown when a user deliberately doesn’t set a value for a certain field (for example, a user can create a custom event and leave its “Issue” field empty, thus the configured “Key” field in a report will be considered not set for such event);
|
“Not applicable” is displayed when a field cannot be assigned a value (for example, when no issue is selected for an event, any of its attributes will be considered not applicable should they be configured as fields for a report).
|
For your convenience, we've implemented the feature to configure the fields that are specific for the Calendar.
The list of Company Calendar fields that can be used in reports but aren’t present in Jira:
Field | For custom event (meetings, business trips, etc.) | For Jira dates event | For worklog event |
|---|---|---|---|
Event Source | The name of a source | ||
Day | The day the start of an event falls on | ||
Week | The week the start of an event falls on | ||
Month | The month the start of an event falls on | ||
Time | Always present in reports as the last column | ||
Event Start/End | The start and end date/time of an event based on a planning source | not available | not available |
Event Reporter | The user who created an event that is based on a custom source | not available | not available |
Event Description | The description for an event that is based on a custom source | not available | not available |
Event Summary | The summary for an event that is based on a custom source | not available | not available |
Event User(s) | The user(s) to whom a custom event is assigned to | not available | not available |
Worklog User | not available | not available | The user who created an event that is based on a worklog source |
Worklog Description | not available | not available | The description for an event that is based on a worklog source |
Worklog Time | not available | not available | The time a user has reported |
Worklog Start/End | not available | not available | The start and end of worklog event |
Worklog Start | not available | not available | The start of worklog event |
Worklog End | not available | not available | The end of worklog event |
Worklog User Email | not available | not available | The email of a user who created a worklog event |
User(s) | The user(s) to whom a custom event is assigned to | The assignee of the issue the event is based on | The user who created a worklog |
Σ Description | The description for an event that is based on a custom source | The description of the issue the event is based on | The description for an event that is based on a worklog source |
Σ Summary | The summary for an event that is based on a custom source | The summary of the issue the event is based on | The summary of the issue a worklog event is based on |
Σ Reporter | The user who created an event that is based on a custom source | The user who reported, in Jira, the issue the event is based on | The user who added a worklog |
Σ Epic | It prints the epic issue key for the epic itself, epic issues and sub-tasks that are part of the epic issues. The common scenario is to group by this field. | ||
Σ Epic Name | It prints the epic name for the epic itself, epic issues and sub-tasks that are part of the epic issues. The common scenario is to group by this field. | ||
Σ Parent | It prints the issue key for the parent issue and sub-tasks that are part of the issue. The common scenario is to group by this field. | ||