Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-27641

Implement history search aka WAS and CHANGED operators for custom fields

    • 95
    • 15
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      Atlassian Update - 23 April 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.

      At this time, this suggestion is not on the JIRA development roadmap. Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      We would like to add support for the "search for issues based on their history"-feature to our custom fields.
      According to https://support.atlassian.com/browse/JSP-121642 this is currently not possible. Currently you only get

      History searches do not support the 'xyz' field.

      So it would be nice if JIRA would support history based searches for custom fields and developers could add it to their custom fields as well.

            [JRASERVER-27641] Implement history search aka WAS and CHANGED operators for custom fields

            Also waiting impatiently for this function. Important for our activity. Thanks.

            Alexandra Palein added a comment - Also waiting impatiently for this function. Important for our activity. Thanks.

            Need it for a filter subscription. The filter should find the issue when a custom checkbox is set recently.

            holger.orth added a comment - Need it for a filter subscription. The filter should find the issue when a custom checkbox is set recently.

            Also vote. Would be great to have it

            Deleted Account (Inactive) added a comment - Also vote. Would be great to have it

            Manuela added a comment -

            Upvoting and waiting for impementation

            Manuela added a comment - Upvoting and waiting for impementation

            A use-case we at Idox encountered for this:

            We use a custom field to capture a valuable information. In an integration with 3rd party application, that field got overridden with some other data. Now we have no way to filter tickets on which a custom field was recently updated.

            Parag Raipuria added a comment - A use-case we at Idox encountered for this: We use a custom field to capture a valuable information. In an integration with 3rd party application, that field got overridden with some other data. Now we have no way to filter tickets on which a custom field was recently updated.

            RakeshG added a comment -

            Please do implement this as this is very much required.  For an instance I am working with XRay and would like to get trend of test cases that were manual and was changed to generic or cucumber to show the trend for every month to generate statistics out of it.   

            RakeshG added a comment - Please do implement this as this is very much required.  For an instance I am working with XRay and would like to get trend of test cases that were manual and was changed to generic or cucumber to show the trend for every month to generate statistics out of it.   

            To add to this, it would be beneficial to know how often or who is updating certain date fields like "Planned end", "Due date" or "Target end" are being updated. 

            Felicia Ainslie added a comment - To add to this, it would be beneficial to know how often or who is updating certain date fields like "Planned end", "Due date" or "Target end" are being updated. 

            I realize the complexity of the ask here (especially when you add in plugin generated fields) but maybe just the basics of text, select, number, date and user fields would cover 95% of the use cases. 

            So maybe now that it's been 6 years and people continue to vote for and ask for this functionality you can place this back on the roadmap?

            For those that have access to the underlying DB, at least we can query the changeitem table. Source

            Matthew Knatz added a comment - I realize the complexity of the ask here (especially when you add in plugin generated fields) but maybe just the basics of text, select, number, date and user fields would cover 95% of the use cases.  So maybe now that it's been 6 years and people continue to vote for and ask for this functionality you can place this back on the roadmap? For those that have access to the underlying DB, at least we can query the changeitem table. Source

            please implement this change, this is very much required

            Mohan Moorkodi added a comment - please implement this change, this is very much required

            Nicola J added a comment -

            If I could double vote for this, I would!

            Nicola J added a comment - If I could double vote for this, I would!

              Unassigned Unassigned
              91cff3f41fd7 uvoellger
              Votes:
              465 Vote for this issue
              Watchers:
              216 Start watching this issue

                Created:
                Updated: