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

          Form Name

            [JRACLOUD-36694] Labels History Search Implementation

            Pinned comments

            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

            Michał Tomasik added a comment - 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

            All comments

            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

            Michał Tomasik added a comment - 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

            Hi all,

            At Paron Forge, we developed a gadget that helps to manage label history - Label Ledger. Just pick a label and project/filter and in the table view, you will see 3 events when the label was:

            • added during issue creation
            • added to an existing issue
            • removed from issue

            Link to the marketplace

            Link to our docs

            Paron Forge added a comment - Hi all, At Paron Forge , we developed a gadget that helps to manage label history - Label Ledger . Just pick a label and project/filter and in the table view, you will see 3 events when the label was: added during issue creation added to an existing issue removed from issue Link to the marketplace Link to our docs

            Such an essential need to have for scope triaging. JUST DO IT ALREADY

            Gregory Smirnov added a comment - Such an essential need to have for scope triaging. JUST DO IT ALREADY

            Is there a reasonable reason?

            Zhangyesen added a comment - Is there a reasonable reason?

            Jarrit added a comment -

            I'd very much like to see this happen to be able to have historic statistics on our tickets.

            Jarrit added a comment - I'd very much like to see this happen to be able to have historic statistics on our tickets.

            apresadi added a comment -

            +1

            apresadi added a comment - +1

            @Jira Team:

            When do you solve this 9 year old ticket?

             

            @Benjamin Steele:

            Do you have a solution or workaround?

            Maximilian Bartesch added a comment - @Jira Team: When do you solve this 9 year old ticket?   @Benjamin Steele: Do you have a solution or workaround?

            +1

            +1

            Miriam Cohen added a comment - +1

            +1 

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

                Created:
                Updated:
                Resolved: