Assigning issue when creating/changing status prevents SLA to start/stop

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • Component/s: SLA
    • None
    • Severity 2 - Major
    • 9

      Summary

      If we create a Service Desk project, if we add an assignee when creating, either with a default assignee or changing it via post-function, the SLAs that start on issue creations are not started.

      This is very sensitive to configuration. We noticed that if we have the default 2 SLAs created for 'Basic' Service Desk project, only one is not started. If we delete one and create another 4, all are started.

       

      This also happens when changing status and assigning at the same time and can prevent SLAs from starting or stopping.

      Steps to Reproduce

      1. Create a Basic Service Desk project
      2. Either add a default Assignee or add a post-function to 'Update field value' to assign the ticket to someone (the post-function must be placed before the event that triggers 'Issue Created' event
      3. Don't change anything else
      4. Create an issue in Customer Portal

      Expected Results

      The issue has both SLA defined by default (Time to Resolution and Time to First Response)

      Actual Results

      It will have only Time to Resolution, but not Time to First Response.

      Notes

      Other changes give different results. For example, if we delete Time to First Response, then it's Time to Resolution that won't appear.

      Workaround

      Remove the operation that's setting the assignee.

            Assignee:
            Dominik Franke
            Reporter:
            Jaime S
            Votes:
            10 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: