Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-22930

Allow more in-depth development field properties for JQL searches

XMLWordPrintable

    • 0
    • 7

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

      Problem Statement:
      Users are currently unable to query for commits via JQL that have been merged or are in other statuses, as the only option open to them is:

      development.[commits].all

      Some users are needing this as they are unable to run JQL searches for specific criteria (such as a JQL that returns issues with commits that have not been merged; JQL for development field based on date/update/author/hash) using the current set of development fields found here.

      Proposed Solution:

      Add other options for commits such as .merged/.notmerged, .open, .date, .author etc. This will allow users with more complex situations to be able to appropriately filter out issues that they may be looking for in larger projects. An example of this could be to enable the list of options in this documentation page: https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-development-fields-reference-973491363.html

            [JSWCLOUD-22930] Allow more in-depth development field properties for JQL searches

            Matthew Hunter added a comment -
            Atlassian Update - December 10, 2024

            Hi everyone,

            Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team - Jira Cloud Product Management

            Matthew Hunter added a comment - Atlassian Update - December 10, 2024 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team - Jira Cloud Product Management

              Unassigned Unassigned
              3176abc1c383 Hieuy Mac
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: