Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-38023

Documentation misleading when field is empty

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • Documentation
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      Jira online documentation is incorrect in regard to the behaviour of JQL when searching for issue not assigned to a given user. Since the official position from Atlassian on the topic of equality being broken for unassigned issues is that it will not change then the online documentation should reflect correct usage.

      The Jira documentation on currentUser https://confluence.atlassian.com/display/JIRA/Advanced+Searching+Functions#AdvancedSearchingFunctions-currentUser%28%29 provides a JQL example that will "find issues that were reported to [sic] me but are not assigned to me"

      reporter = currentUser() and assignee != currentUser()

      however this will not return issues that are unassigned.

      It is likely the example JQL should be :

      reporter = currentUser() AND (assignee != currentUser() OR assignee is EMPTY)

      Personally, I would prefer it if JQL were fixed but failing that the docs should be updated.

      I would encourage you to update docs with a description of "correct" usage of JQL where a field is empty as it is counter intuitive that logical operators should behave this way.

              skarp Sarah Karp
              850658b662a4 Ewan Willis
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: