-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
1
-
3
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Currently, JIRA Service Desk SLA will still retain how long has it been runnin even it is moved to another SLA. When it is stopped and start the SLA again, there will be a box beside the SLA letting the Agent now how long has it been elapsed until it the SLA stop which is good.
But, it will be great if we could SUM the total of how long the SLA have been elapsed whether when for Cycles that the SLA Met or Not. Then, generating a Report for it as well about the Issue SLA Changes.
- relates to
-
JSDCLOUD-1812 Sum of the SLA Cycle of an Issue including the Report
- Closed
Form Name |
---|
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