-
Bug
-
Resolution: Won't Fix
-
Medium
-
None
-
3.1.0, 3.2.0
-
Severity 2 - Major
-
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Issue Summary
If a user resolves an issue in Service Desk and sets a resolution, if the workflow also contains a post function to set resolution, the SLA for the issue would not stop running.
Steps to Reproduce
- Create a Service Desk Project.
- Modify the workflow for the project created above.
- Add a post function of type update field to resolve issue transitions.
- Select option Resolution and Select any of the available resolutions.
- Save the workflow and publish your changes.
- Create a ticket in the project.
- Resolve the ticket through the Agent view.
NOTE
This is only reproducible if the transition the agent uses to close the request includes a screen where the resoulution field is set
Expected Behavior
JIRA would set the resolution and stop the SLA.
Actual Behaviour
JIRA would set the resolution but it would not stop the SLA.
Workaround
Remove either the post function or the field from the screen (or the screen completely from the transition).
- duplicates
-
JSDSERVER-4038 Setting resolution twice is preventing 'Resolve Issue' notification in SD
-
- Closed
-
-
JSMDC-384 You do not have permission to view this issue
- relates to
-
JSDCLOUD-4405 SLA Keeps Running Bug
-
- Closed
-
- was cloned as
-
JSDA-1019 Failed to load
[JSDSERVER-4405] SLA Keeps Running Bug
Remote Link | Original: This issue links to "JSDS-384 (JIRA Server (Bulldog))" [ 274073 ] | New: This issue links to "JSMDC-384 (JIRA Server (Bulldog))" [ 274073 ] |
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2305354 ] | New: JAC Bug Workflow v3 [ 3126158 ] |
Symptom Severity | Original: Major [ 14431 ] | New: Severity 2 - Major [ 15831 ] |
Workflow | Original: JSD Bug Workflow v5 [ 2059308 ] | New: JSD Bug Workflow v5 - TEMP [ 2305354 ] |
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2056728 ] | New: JSD Bug Workflow v5 [ 2059308 ] |
Workflow | Original: JSD Bug Workflow v5 [ 1956488 ] | New: JSD Bug Workflow v5 - TEMP [ 2056728 ] |
Workflow | Original: JSD Bug Workflow v4 [ 1615376 ] | New: JSD Bug Workflow v5 [ 1956488 ] |
Description |
Original:
+Issue Summary+
If a user resolves an issue in Service Desk and sets a resolution, if the workflow also contains a post function to set resolution, the SLA for the issue would not stop running. +Steps to Reproduce+ # Create a Service Desk Project. # Modify the workflow for the project created above. # Add a post function of type {{update field}} to {{resolve issue}} transitions. # Select option {{Resolution}} and Select any of the available resolutions. # Save the workflow and publish your changes. # Create a ticket in the project. # Resolve the ticket through the Agent view. NOTE This is only reproducible if the transition the agent uses to close the request includes a screen where the resoulution field is set +Expected Behavior+ JIRA would set the resolution and stop the SLA. +Actual Behaviour+ JIRA would set the resolution but it would not stop the SLA. +Workaround+ Remove either the post function or the field from the screen (or the screen completely from the transition). |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-4405]. {panel} +Issue Summary+ If a user resolves an issue in Service Desk and sets a resolution, if the workflow also contains a post function to set resolution, the SLA for the issue would not stop running. +Steps to Reproduce+ # Create a Service Desk Project. # Modify the workflow for the project created above. # Add a post function of type {{update field}} to {{resolve issue}} transitions. # Select option {{Resolution}} and Select any of the available resolutions. # Save the workflow and publish your changes. # Create a ticket in the project. # Resolve the ticket through the Agent view. NOTE This is only reproducible if the transition the agent uses to close the request includes a screen where the resoulution field is set +Expected Behavior+ JIRA would set the resolution and stop the SLA. +Actual Behaviour+ JIRA would set the resolution but it would not stop the SLA. +Workaround+ Remove either the post function or the field from the screen (or the screen completely from the transition). |
Link |
New:
This issue relates to |
Remote Link | New: This issue links to "JSDS-384 (JIRA Server (Bulldog))" [ 274073 ] |