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

Search the change history

XMLWordPrintable

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

      Many people wish to be able to search for issues that have been in some state in the past. For example, all issues that have once been Reopened.

          Form Name

            [JRASERVER-5536] Search the change history

            Samantha Colborn added a comment -

            +1 to "component was in (...)"

            Samantha Colborn added a comment - +1 to "component was in (...)"

            alberto added a comment -

            +1 to "component was in (...)AND labels was in
            https://jira.atlassian.com/secure/AddComment!default.jspa?id=22405

            alberto added a comment - +1 to "component was in (...)AND labels was in https://jira.atlassian.com/secure/AddComment!default.jspa?id=22405

            SMAtlassianMber added a comment -

            +1 to "component was in (...)"

            SMAtlassianMber added a comment - +1 to "component was in (...)"

            Dave Manningsmith added a comment -

            +1 to "component was in (...)"

            Dave Manningsmith added a comment - +1 to "component was in (...)"

            Danny added a comment -

            I would like to use this for the following: 

            component was in (...)

            Danny added a comment - I would like to use this for the following: component was in (...)

            bill.fuller@nexenta.com added a comment -

            Need to be able to query history on Release #s. We have a "Target Release" field. I can see that this was changed in history tab, but can't find a way to query for "Target Release" was in ....

            bill.fuller@nexenta.com added a comment - Need to be able to query history on Release #s. We have a "Target Release" field. I can see that this was changed in history tab, but can't find a way to query for "Target Release" was in ....

            Gayathry Manikandan added a comment -

            Hello there,

            I have a requirement to query based on labels within a certain date range. For eg., I want the list of tickets to which the label "regression" was added between say Feb 01 2017 and Mar 08 2017. Could you please advise on how we can  achieve this? 

            Thanks,

            GAyathry

             

            Gayathry Manikandan added a comment - Hello there, I have a requirement to query based on labels within a certain date range. For eg., I want the list of tickets to which the label "regression" was added between say Feb 01 2017 and Mar 08 2017. Could you please advise on how we can  achieve this?  Thanks, GAyathry  

            Vikram added a comment -

            Thank you , this is working awesome..

            Vikram added a comment - Thank you , this is working awesome..

            Amro Hassaan added a comment -

            +1 on this long awaited feature. It is definitely needed in my company. I need to search for previous fixversion(s) of issues for reporting.

            Amro Hassaan added a comment - +1 on this long awaited feature. It is definitely needed in my company. I need to search for previous fixversion(s) of issues for reporting.

            John Crim added a comment -

            Also, you can make queries like:

            status was Resolved by "user.name"

            which is a type of change history query.

            John Crim added a comment - Also, you can make queries like: status was Resolved by "user.name" which is a type of change history query.

              Unassigned Unassigned
              7ee5c68a815f Jeff Turner
              Votes:
              355 Vote for this issue
              Watchers:
              225 Start watching this issue

                Created:
                Updated:
                Resolved: