-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
2.6.0-OD-04
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
When setting an automated rule using the SLA breach event, it fails some times.
Steps to reproduce:
Expected Result: All issues are transitioned when SLA is breached
Actual: Some issues are not transitioned at 0:00 when SLA is breached.
A search for issues with the SLA column will show many issues in 0:00 but some of them with negative numbers that would mean that the Transition didn't occur in time.
- is duplicated by
-
JSDSERVER-3682 SLA's time promise is not scheduled correctly after updating
-
- Closed
-
- is related to
-
JSDSERVER-2141 JQL functions not working in Atlassian Scheduler API
-
- Closed
-
-
DESK-4349 Failed to load
- relates to
-
JSDCLOUD-2083 SLA breach event is not triggered intermittently
-
- Closed
-
- was cloned as
-
DESK-4323 Loading...
[JSDSERVER-2083] SLA breach event is not triggered intermittently
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2305234 ] | New: JAC Bug Workflow v3 [ 3125932 ] |
Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
Labels | Original: affects-cloud affects-server cst | New: affects-cloud affects-server |
Labels | Original: affects-cloud affects-server | New: affects-cloud affects-server cst |
Workflow | Original: JSD Bug Workflow v5 [ 2059178 ] | New: JSD Bug Workflow v5 - TEMP [ 2305234 ] |
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2056585 ] | New: JSD Bug Workflow v5 [ 2059178 ] |
Workflow | Original: JSD Bug Workflow v5 [ 1956223 ] | New: JSD Bug Workflow v5 - TEMP [ 2056585 ] |
Workflow | Original: JSD Bug Workflow v4 [ 1615652 ] | New: JSD Bug Workflow v5 [ 1956223 ] |
Description |
Original:
When setting an automated rule using the SLA breach event, it fails some times.
*Steps to reproduce:* # Configure an Automation to Transition issues when the SLA is breached like the example: !Screen Shot 2015-07-09 at 2.45.51 PM.png|thumbnail! !Screen Shot 2015-07-09 at 2.46.00 PM.png|thumbnail! *Expected Result:* All issues are transitioned when SLA is breached *Actual:* Some issues are not transitioned at 0:00 when SLA is breached. A search for issues with the SLA column will show many issues in 0:00 but some of them with negative numbers that would mean that the Transition didn't occur in time. |
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-2083]. {panel} When setting an automated rule using the SLA breach event, it fails some times. *Steps to reproduce:* # Configure an Automation to Transition issues when the SLA is breached like the example: !Screen Shot 2015-07-09 at 2.45.51 PM.png|thumbnail! !Screen Shot 2015-07-09 at 2.46.00 PM.png|thumbnail! *Expected Result:* All issues are transitioned when SLA is breached *Actual:* Some issues are not transitioned at 0:00 when SLA is breached. A search for issues with the SLA column will show many issues in 0:00 but some of them with negative numbers that would mean that the Transition didn't occur in time. |
Link |
New:
This issue relates to |
Labels | Original: affects-cloud | New: affects-cloud affects-server |