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

Disabling Smart Query in JIRA would be helpful

XMLWordPrintable

    • 19
    • 8

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

      Status update 2023/06/22

      Hi all,

      We are pleased to inform you that the rollout to turn off Smart Query by default is completed. Customers on release tracks will get this feature in August (July for the preview track).

      To enable Smart Query, head over to your profile on top right > Personal Settings , and find “Quick search smart queries” under “Jira Labs”. Read more about smart query here.

      Thank you for your patience.

      Cheers,
      Jason.

       

      Current Behavior:
      Smart Query has, on more than one occasion, ruined a perfectly good search with its smartness.

      There have been zero occasions where I have found it useful.

      For example, if I search for "duplicate x", I want to find bugs in my software where something is getting duplicated. IE, "duplicate records" or "duplicate users" or "duplicate locations".

      I am not looking for JIRA issues that are duplicate. And by automagically changing my filter to issue type of duplicate is just wrong.

      Desired Behavior:
      Add a feature to turn this silliness off.

      Steps to Reproduce:
      1. In the Search Box in the upper right hand corner, type in "Duplicate something".
      2. Search.
      3. Note that a filter has been set for Duplicate Issues.
      Thanks

              4b7910ae10b4 April Chi
              c6739c4a7737 Patrick Henry
              Votes:
              94 Vote for this issue
              Watchers:
              67 Start watching this issue

                Created:
                Updated:
                Resolved: