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

Allow JQL searches via the Issue Navigator to skip validation and return partial results

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • JQL
    • 5
    • 14
    • 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.

      As a user I would like to be able to run parsing but "invalid" queries (there is a mistyped / non-visible / deleted issue key, version name, project key ...) and still obtain "partial" results.

      As this might be a genuine mistake that the user would like to correct (a typo for instance), we should ensure that a visible warning is displayed in the UI explaining that the result set might not be complete and listing out the "invalid" values.

      That way the user can opt to either "correct" the query or use the results as they are.

      For some use cases, the validation errors don't really matter as the use cases are for instance: "return issues with keys including x,y,z if they exist ..." so the non-existence of one of the issues in the list is not really a problem for the user executing the query.

      Currently, the REST API exposes a validateQuery param to skip validation. When this issue is implemented, we must ensure that the behaviour of the search REST interface is consistent with the changes done under this issue.

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-20916 Shared filter queries don't work with "Filter Result" gadget if login user doesn't have browse permission on one of the projects.

          • Medium - Medium priority issues
          • Gathering Impact
          incorporates

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

          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-39800 JQL should not fail when project is hidden

          • Low - Low priority issues
          • Closed

          Suggestion - JRASERVER-35351 Change message displayed in Issue Navigator for projects without browse permission

          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-41253 JQL filter False Error: Project doesn't exist should be no permission

          • Low - Low priority issues
          • Closed
          relates to

          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 - JRASERVER-33031 Issuekey in JQL search should have an option to not fail if issuekey doesn't exist

          • Closed

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

          • Gathering Interest

          Activity

            People

              Unassigned Unassigned
              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              Votes:
              86 Vote for this issue
              Watchers:
              67 Start watching this issue

              Dates

                Created:
                Updated: