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

Details

    • 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.

    Description

      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.

      Attachments

        Issue Links

          causes

          Suggestion - BAM-9882 Bamboo does not list JIRA issue details if one or more issue keys is invalid in the commit message

          • Closed
          duplicates

          Suggestion - JRASERVER-33031 Issuekey in JQL search should have an option to not fail if issuekey doesn't exist

          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-36802 Using OR statement in JQL where issue key doesn't exist doesn't return values

          • Low - Low priority issues
          • Closed

          Suggestion - JRASERVER-30245 Have JIRA Search Function Return Results When Searching Legacy Issue Keys

          • Closed
          is incorporated by

          Suggestion - JRASERVER-40245 Allow JQL searches via the Issue Navigator to skip validation and return partial results

          • Gathering Interest
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-30678 JQL search for list of issue keys fails if single issue key missing / changed

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-71762 JQL search with 25 keys vs 26 keys results in different behavior when an issue doesn't exist

          • Low - Low priority issues
          • Gathering Impact

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

          • Closed
          clones

          JRADEV-16838 Loading...

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: