JQL "is Empty" and "is not empty" does not work for Security level unless it has been changed previously in Team-managed projects

XMLWordPrintable

    • 1
    • Severity 3 - Minor

      Issue Summary

      JQL "is Empty" and "is not empty" does not work for Security level unless it has been changed previously in Team-managed projects

      Steps to Reproduce

      1. Create a Team managed project
      2. Create an issue in the project without any security level
      3. Go to JQL/Advanced search, add the column Security level, and then search for the issue, you will see the Security field is empty.
      4. Once you have the issue in your search result add "and level is empty" to the JQL query and run the search.

      Expected Results

      The issue created in step 2 still is in the search results.

      Actual Results

      The issue does not appear in the search results.

      Notes:

      • If we add a security level to the issue to restrict visibility by role,  the JQL "and level is not empty" will start working.
      • If we add a security level to the issue, then remove it, and then use "and level is empty", it will return the expected results.
      • From these results it seems as if it was needed for the Security level field to be modified at least once for the "exists" operator to work as expected.

      Workaround

      Modify the Security level in the issue to "enable" empty/is not empty to work as expected.

            Assignee:
            Unassigned
            Reporter:
            Rene C. [Atlassian Support] (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: