-
Suggestion
-
Resolution: Duplicate
-
None
-
None
-
None
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Currently, we could create an SLA/Metric as we like including the goals and condition. But, there is sometimes where the Agents is confused on why some close issue does not have a specific Metric/SLA that have been configured in the project, even though the conditions are met. As we know that SLA could not be changes or updated for a Closed issue, this could create a confusion among the agents on a particular service desk project if one of the agents are making changes without notifying the other agents.
Hence, it would be great if we could see the date of SLA/Metrics when it is created and update on the UI so the agents could know the reason why some of the issue is not having the SLA appearing in the JIRA Issue view.
- is duplicated by
-
JSDSERVER-494 Service needs an SLA configuration audit trail and a issue history of the SLA config that was in play
- Closed
- relates to
-
JSDCLOUD-1648 The Date information about when an SLA/Metrics is Created and Updated
- Closed
[JSDSERVER-1648] The Date information about when an SLA/Metrics is Created and Updated
Workflow | Original: JAC Suggestion Workflow [ 3011703 ] | New: JAC Suggestion Workflow 3 [ 3649225 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2665028 ] | New: JAC Suggestion Workflow [ 3011703 ] |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2322252 ] | New: Confluence Workflow - Public Facing v4 [ 2665028 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JSD Suggestion Workflow [ 2053623 ] | New: JSD Suggestion Workflow - TEMP [ 2322252 ] |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2048776 ] | New: JSD Suggestion Workflow [ 2053623 ] |
Workflow | Original: JSD Suggestion Workflow [ 1280580 ] | New: JSD Suggestion Workflow - TEMP [ 2048776 ] |
Description |
Original:
Currently, we could create an SLA/Metric as we like including the goals and condition. But, there is sometimes where the Agents is confused on why some close issue does not have a specific Metric/SLA that have been configured in the project, even though the conditions are met. As we know that SLA could not be changes or updated for a Closed issue, this could create a confusion among the agents on a particular service desk project if one of the agents are making changes without notifying the other agents.
Hence, it would be great if we could see the date of SLA/Metrics when it is created and update on the UI so the agents could know the reason why some of the issue is not having the SLA appearing in the JIRA Issue view. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-1648]. {panel} Currently, we could create an SLA/Metric as we like including the goals and condition. But, there is sometimes where the Agents is confused on why some close issue does not have a specific Metric/SLA that have been configured in the project, even though the conditions are met. As we know that SLA could not be changes or updated for a Closed issue, this could create a confusion among the agents on a particular service desk project if one of the agents are making changes without notifying the other agents. Hence, it would be great if we could see the date of SLA/Metrics when it is created and update on the UI so the agents could know the reason why some of the issue is not having the SLA appearing in the JIRA Issue view. |
Link |
New:
This issue relates to |
Workflow | Original: TTT: Simple Issue Tracking Workflow [ 841420 ] | New: JSD Suggestion Workflow [ 1280580 ] |
Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |