Company Calendar Planner for Jira v 5.7.x: Reports
Did you know that you can generate reports based on created events in Company 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 next screen. Here, you can configure the fields to be displayed in reports.
The four fields are configured for the reports by default. These are: Project, Key, Day, and User(s).
You can add, remove or rearrange the fields by using drag-and-drop, on the report fields configuration.
Before generating a report, please make sure that all required sources and users are enabled, on the left panel.
In addition, make sure to check the selected start and end dates.
Starting app version 5.6.x, a custom period can be selected, in reports, besides the standard periods such as day, week, month and quartal.
Click the Generate report button to generate a report:
The generated report has static header and footer. This comes handy when a generated report contains a lot of data.
For your convenience, we've also implemented the feature to add the fields that are specific for the Company 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 |
|---|---|---|
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 | |
Event Reporter | The user who created an event that is based on a custom source | not available |
Event Description | The description for an event that is based on a custom source | not available |
Event Summary | The summary for an event that is based on a custom source | not available |
Event User(s) | The user(s) to whom a custom event is assigned to | not available |
Time | Always present in reports as the last column | |
User(s) | The user(s) to whom a custom event is assigned to | The assignee of the issue the event is based on |
Σ Description | The description for an event that is based on a custom source | The description of the issue the event is based on |
Σ Summary | The summary for an event that is based on a custom source | The summary of the issue the 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 |
Σ 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. | |