NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
I have a complaint about SLA reports of JIRA Service Desk and I think this should be classified as a bug as I don't want to believe it was designed this way.
The reports tab of JSD service provider interface show line charts about number of created, resolved tickets for past 7 days, 30 days, etc. As far as I understand, report filters tickets based on createddate and resolveddate of the issues. The annoying thing is, if I select a report for the past 7 days and run the report at say ... 10:00 AM, the date filter includes records for the past 6x24 hours. There are two things wrong with this:
1- There appears to be names of 7 days shown on the report but there are actually 6 days on the report (6x24) The first and last days are incomplete. The rest of "today" is not lived yet and more importantly the "first day" only includes tickets after 10:00 AM of that day. This is not obvious for the customers, they expect full days.
2 - As time passes through the day, I cannot have the same report again. Every minute passing changes my report from the starting point, filtering tickets according to a moving point in the middle of the day, so my reports are inconsistent.
The reports should allow me to set beginning and ending dates of reports and more importantly reports must contain full 24 hours for any day shown on report.
Problem Definition
Service Desk's Report only allows a specific range on filtering the Report period. As an example, the 7 days report will show the following information:
| 6 days ago | 5 days ago | 4 days ago | 3 days ago | 2 days ago | Yesterday | Today |
|---|---|---|---|---|---|---|
| 00:00 - 23:59 | 00:00 - 23:59 | 00:00 - 23:59 | 00:00 - 23:59 | 00:00 - 23:59 | 00:00 - 23:59 | 00:00 - 23:59 |
As today has not yet finished, the data can change each time the report is generated.
Suggested Solution
Ability to provide custom ranges for the Report period
Why this is important
Allow the user to extract and focus on the important details from the report.
- relates to
-
JSDCLOUD-421 Date parameters of SLA Reports are irrational
- Closed
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-421] Allow custom range for Report for a more detailed results
| Resolution | Original: Won't Do [ 10000 ] | New: Low Engagement [ 10300 ] |
| Status | Original: Closed [ 6 ] | New: Closed [ 6 ] |
| Resolution | New: Won't Do [ 10000 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| UIS | Original: 1 | New: 0 |
| Remote Link | New: This issue links to "Page (Confluence)" [ 505101 ] |
| Workflow | Original: JAC Suggestion Workflow [ 3012208 ] | New: JAC Suggestion Workflow 3 [ 3649662 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2664848 ] | New: JAC Suggestion Workflow [ 3012208 ] |
| UIS | Original: 0 | New: 1 |
| UIS | Original: 1 | New: 0 |
| Support reference count | New: 3 |
Hi,
Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.
This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).
We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.
To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.
Regards,
Jira Service Management, Server & Data Center