• Type: Bug
• Resolution: Duplicate
• Priority: Low
• Fix Version/s: 3.6.4
• Affects Version/s: 3.4.0
• Component/s: SLA
• Labels:

  None

[JSDSERVER-5312] SLA Caching leads to SLAs overwriting Each Other

Owen made changes - 27/Mar/2019 5:47 AM

Workflow	Original: JSD Bug Workflow v5 - TEMP [ 2420225 ]	New: JAC Bug Workflow v3 [ 3126126 ]
Status	Original: Done [ 10044 ]	New: Closed [ 6 ]

Owen made changes - 24/Oct/2018 5:04 AM

Symptom Severity

Original: Major [ 14431 ]

New: Severity 2 - Major [ 15831 ]

Matthew McMahon (Inactive) made changes - 06/Sep/2017 1:31 AM

Fix Version/s		New: 3.6.4 [ 73825 ]
Fix Version/s	Original: 3.7.0 [ 72395 ]
Resolution		New: Duplicate [ 3 ]
Status	Original: Untriaged [ 11672 ]	New: Done [ 10044 ]

Matthew McMahon (Inactive) made changes - 06/Sep/2017 1:31 AM

Link

New: This issue duplicates JSDSERVER-5299 [ JSDSERVER-5299 ]

Ismael Olusula Jimoh (Inactive) made changes - 09/Aug/2017 11:28 AM

Fix Version/s

New: 3.7.0 [ 72395 ]

Ismael Olusula Jimoh (Inactive) made changes - 09/Aug/2017 11:25 AM

Description

New: h5. Issue Summary When an issue transitions to a condition that is meant to meet a complete condition for an SLA, there are times the SLA would simply start to count again. h5. Environment JIRA Service Desk 3.4.x h5. Steps to Reproduce # Setup the time to resolution condition in a JIRA Project. # Transition an issue to a status such as done to meet the condition for the SLA to be met. (!) Reproducing this issue is difficult since it happens randomly, however the above steps match the use case. h5. Expected Behavior JIRA would mark the SLA as done and it would stop counting. h5. Actual Behavior For some reason, JIRA would mark the SLA as done and after a while, it would start to count.

Ismael Olusula Jimoh (Inactive) created issue - 09/Aug/2017 11:20 AM