• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • SLA
    • 8
    • 7
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      The field used to store the SLA value only has numeric operators, but no "is empty" test.

      Step to reproduce :

      • Configure an SLA in a way some of the requests are not matched
      • Try to create a JQL expression specifically matching the missed issues.

      Needed for :

      • Checking that the JSD admins / project admins are not missing any issues in the SLA configurations.
      • Checking the SLA configuration matches a specific set of issues

      Related to : https://answers.atlassian.com/questions/46082572

      Affects Versions : 1.2.6.1, 3.2.7, 3.3.0

      Workaround

      1. Create a saved filter like "My SLA Not Empty" with JQL like: project = MYPROJECT AND filter != "My SLA Not Empty"
      2. Reference the saved filter in a NOT query: project = MYPROJECT AND filter != "My SLA Not Empty"

      https://community.atlassian.com/t5/Jira-questions/Find-issues-with-specific-SLA-field-beeing-empty/qaq-p/261489#U77355

            [JSDSERVER-4650] Add an "is empty" operator on the JSD "SLA" field type.

            To match what Jira can currently do with SLA, and not having to let Atlassian develop the 'is empty' check, one solution would be to have the function empty() that would return true if this SLA is not set.

            Jean-Michel Bernard added a comment - To match what Jira can currently do with SLA, and not having to let Atlassian develop the 'is empty' check, one solution would be to have the function empty() that would return true if this SLA is not set.

            Andrey Kiyanovskiy added a comment - - edited

            There is nonsense in the Workaround section. The saved filter has to be like:

            project = MYPROJECT AND ("My SLA" = breached() OR "My SLA" != breached())

            Andrey Kiyanovskiy added a comment - - edited There is nonsense in the Workaround section. The saved filter has to be like: project = MYPROJECT AND ("My SLA" = breached() OR "My SLA" != breached())

            We currently have an open ticket with Atlassian Support where SLAs are randomly not being set (i.e. empty).  There is a REST API to fix them but I have no way to detect them since there is no "is EMPTY" operator for this field.   It is an inconsistency that must be fixed.

            Brent Webster added a comment - We currently have an open ticket with Atlassian Support where SLAs are randomly not being set (i.e. empty).  There is a REST API to fix them but I have no way to detect them since there is no "is EMPTY" operator for this field.   It is an inconsistency that must be fixed.

              Unassigned Unassigned
              aa669d2c261c Corentin Méhat
              Votes:
              111 Vote for this issue
              Watchers:
              38 Start watching this issue

                Created:
                Updated: