Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-23287

Searching for an issue key that doesn't exist with JQL should not cause a query/validation error.

XMLWordPrintable

    • We collect Jira 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 Server. Using JIRA Cloud? See the corresponding suggestion.

      If you do a jql search for more than one specific issue key and one of those keys does not exist, it derails the whole search.

      For example, imagine you want to find information on two issues. One with key TST-1 and one with key CONF-1747. You use a query like this:

      issuekey in (TST-1, CONF-1747)

      Let's say that TST-1 does not exist. Instead of only returning CONF-1747, the search screen displays an error. This is unintuitive behavior. Consider the query in a different form. 

      issuekey IN TST-1 OR issuekey IN CONF-1747

      There is an issue that matches the above criteria but the JQL engine returns an error because there is no TST-1 key.

      The particular use case is the jiraissues macro in Confluence. In Confluence 3.5, users will be able to use it to display info for single issue keys. I want to create a single JQL query request for all issues on a page. However, if a user mistypes a single key, it will derail the entire search request to JIRA and no information will be returned.

              Unassigned Unassigned
              rackley RyanA
              Votes:
              6 Vote for this issue
              Watchers:
              22 Start watching this issue

                Created:
                Updated:
                Resolved: