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

          1.
          JQL editor cannot handle complex requests Sub-task Closed Unassigned
          2.
          JQL query -- 'dates' clause similar to 'text' clause - e.g., search for date matches from any of many date fields Sub-task Closed Unassigned
          3.
          Add Project Category in the simple (or JQL) searchable criteria in the Project selection box Sub-task Closed Unassigned
          4.
          JQL - Add wildcard functionality to versions Sub-task Closed Unassigned
          5.
          Provide the ability to search for a range of versions within JQL Sub-task Closed Unassigned
          6.
          Ability to join results from two filters and display the combined output using JQL. Sub-task Closed Unassigned
          7.
          Allow searching by number of Components / Versions Sub-task Closed Unassigned
          8.
          JQL component picker should show relevant components Sub-task Closed Unassigned
          9.
          Allow JQL to query other Atlassian products Sub-task Closed Unassigned
          10.
          Option to search in JIRA without stemming words. Sub-task Closed Unassigned
          11.
          Add the ability to filter votes by the time the vote was cast... Sub-task Closed Unassigned
          12.
          Add a JQL function to filter issues by the number of comments... Sub-task Closed Unassigned
          13.
          Enable searching comments and descriptions by email domain Sub-task Closed Unassigned
          14.
          As a Jira user I would like the now() search function to support time increment Sub-task Closed Unassigned
          15.
          Allow endOfWeek() JQL function to take a date as the argument Sub-task Closed Unassigned
          16.
          JQL - Add wildcard functionality to labels Sub-task Closed Unassigned
          17.
          Ability to have CHANGED operator compatible with Due Date field Sub-task Closed Unassigned
          18.
          Inline documentation for JQL query functions Sub-task Closed Unassigned
          19.
          Ability to have CHANGED operator for (specifically configured) custom fields Sub-task Closed Unassigned
          20.
          Change semantics of JQL "was" operator to exclude issues that currently have the given value. Sub-task Closed Unassigned

            [JRACLOUD-23288] List of suggested JQL improvements

            Hey All voters and watchers, you can also vote for this issue as it's related :

            https://jira.atlassian.com/browse/JRA-64868

            Cheers

            Support NEOFI added a comment - Hey All voters and watchers, you can also vote for this issue as it's related : https://jira.atlassian.com/browse/JRA-64868 Cheers

            Thanks for taking the time to raise this issue.

            Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

            I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

            Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.
            Kind Regards,
            Kerrod Williams
            JIRA Product Management
            kerrod.williams at atlassian dot com

            Kerrod Williams (Inactive) added a comment - Thanks for taking the time to raise this issue. Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts . In part, that means concentrating on those issues that resonate the most with our users. I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue. Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me. Kind Regards, Kerrod Williams JIRA Product Management kerrod.williams at atlassian dot com

              Unassigned Unassigned
              rkrishna Roy Krishna (Inactive)
              Votes:
              7 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: