Details

    • Type: Suggestion
    • Status: Closed (View Workflow)
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: JQL
    • Labels:
      None
    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      Attachments

      1.
      JQL editor cannot handle complex requests Sub-task Closed Unassigned
       
      2. Search for sub-tasks with parent related conditions [Advanced Queries] Sub-task Open Unassigned
       
      3. Ability to search for all issues that are linked to (i.e. blocking) by any issue Sub-task Open Unassigned
       
      4.
      JQL query -- 'dates' clause similar to 'text' clause - e.g., search for date matches from any of many date fields Sub-task Closed Unassigned
       
      5.
      Add Project Category in the simple (or JQL) searchable criteria in the Project selection box Sub-task Closed Unassigned
       
      6. JQL - Add wildcard functionality to versions Sub-task Open Unassigned
       
      7. Create JQL currentProject() function Sub-task Open Unassigned
       
      8.
      Provide the ability to search for a range of versions within JQL Sub-task Closed Unassigned
       
      9. In the issue navigator, component field should support the operator '~' Sub-task Open Unassigned
       
      10. Ability to join results from two filters and display the combined output using JQL. Sub-task Open Unassigned
       
      11. Allow searching by number of Components / Versions Sub-task Open Unassigned
       
      12.
      JQL component picker should show relevant components Sub-task Closed Unassigned
       
      13. Allow JQL to query other Atlassian products Sub-task Open Unassigned
       
      14. JQL to find issues that have exactly only one fixVersion Sub-task Open Unassigned
       
      15. JQL function to see if a fixVersion has a release date defined (EMPTY) Sub-task Open Unassigned
       
      16. unreleasedVersions() shouldn't include archived versions Sub-task Open Unassigned
       
      17.
      Option to search in JIRA without stemming words. Sub-task Closed Unassigned
       
      18.
      Add the ability to filter votes by the time the vote was cast... Sub-task Closed Unassigned
       
      19.
      Add a JQL function to filter issues by the number of comments... Sub-task Closed Unassigned
       
      20.
      Enable searching comments and descriptions by email domain Sub-task Closed Unassigned
       
      21.
      As a Jira user I would like the now() search function to support time increment Sub-task Closed Unassigned
       
      22.
      Allow endOfWeek() JQL function to take a date as the argument Sub-task Closed Unassigned
       
      23.
      JQL - Add wildcard functionality to labels Sub-task Closed Unassigned
       
      24.
      Ability to have CHANGED operator compatible with Due Date field Sub-task Closed Unassigned
       
      25.
      Inline documentation for JQL query functions Sub-task Closed Unassigned
       
      26. Enable searching of issues where comments are empty Sub-task Open Unassigned
       
      27. Retain the extra bracket on the advanced search when saving a filter Sub-task Open Unassigned
       
      28.
      Ability to have CHANGED operator for (specifically configured) custom fields Sub-task Closed Unassigned
       
      29.
      Change semantics of JQL "was" operator to exclude issues that currently have the given value. Sub-task Closed Unassigned
       

        Activity

        Hide
        kewilliams Kerrod Williams 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

        Show
        kewilliams Kerrod Williams 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

          People

          • Assignee:
            Unassigned
            Reporter:
            rkrishna Roy Krishna [Atlassian]
          • Votes:
            7 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: