Issue Summary

The SLA incorrectly unpauses when it is configured with 2 pause conditions, and then an issue changes from verifying 2 pause conditions to only 1 pause condition.

Steps to replicate

• Install Jira Service Management (JSM) on 5.0.0
• Create a new JSM project
• Create a new SLA with:
  • "issue created" as the start condition
  • the 2 pause conditions listed below:
    • Status: Waiting for customer
    • Assignee: Set
  • any stop condition
    
• Create a new issue in the JSM project
  • Verify that the SLA is ticking as expected
    
• Transition it to "Waiting for customer"
  • Verify that the SLA is paused as expected
    
• Set the assignee field to any user
  • Verify that the SLA is still paused as expected
    
• Clear the assignee field

Expected behavior

The SLA should still be paused due to the condition "Status: Waiting for customer"

Actual behavior

The SLA starts ticking again

Workaround

No known workaround at the moment.

Also, note that recalculating the SLA from the Jira issue view page using the button ... > Recalculate all SLAs does not fix the SLA