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

Labels History Search Implementation

XMLWordPrintable

    • 13
    • 5

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

      Atlassian Update – 19 August 2024

      Hi everyone,

      Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future.

      Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.

      We understand that our decision may be disappointing. Please don't hesitate to contact us if you have any questions or feedback.

      Regards,
      Michał Tomasik
      Software Engineer, Jira Cloud

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Currently in JIRA, you cannot use the history search queries on a label field. Our company uses the label field to mark items in the scope of a fix version and would like to be able to search for label changes (i.e. labels changed AFTER startOfDay()). This would be a critical help to tracking unapproved additions to our scope.

              Unassigned Unassigned
              66a1116b01df Benjamin Steele
              Votes:
              95 Vote for this issue
              Watchers:
              62 Start watching this issue

                Created:
                Updated:
                Resolved: