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

Ability to use operator WAS / WAS IN / WAS NOT / WAS NOT IN in custom fields

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • 12
    • 16

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

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

      Currently, these operators can be used with the Assignee, Fix Version, Priority, Reporter, Resolution and Status fields only when using JQL. It would make a good improvement to have those working for custom fields as well (e.g multi-select fields).

        1. 100-105 Exam Questions.pdf
          722 kB
        2. 200-105 Exam Questions.pdf
          245 kB
        3. 200-125 Exam Questions.pdf
          606 kB
        4. 210-250 Exam Questions.pdf
          183 kB
        5. 210-255 Exam Questions.pdf
          329 kB
        6. 210-451 Exam Questions.pdf
          184 kB
        7. 210-455 Exam Questions.pdf
          184 kB
        8. 220-1001 Exam Questions.pdf
          261 kB
        9. 220-1002 Exam Questions.pdf
          184 kB

            [JRACLOUD-34103] Ability to use operator WAS / WAS IN / WAS NOT / WAS NOT IN in custom fields

            Anusha Rutnam added a comment -
            Atlassian Update - August 2023

            After some analysis, we've found that this ticket is a duplicate of the request JRACLOUD-27641 – Implement history search aka WAS and CHANGED operators for custom fields which has more votes.

            We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - Atlassian Update - August 2023 After some analysis, we've found that this ticket is a duplicate of the request JRACLOUD-27641 – Implement history search aka WAS and CHANGED operators for custom fields which has more votes. We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Grace D added a comment -

            +1

            Grace D added a comment - +1

            Scott Gast added a comment -

            +1

            Scott Gast added a comment - +1

            Bill Gould added a comment -

            Would be very useful to add this

            Bill Gould added a comment - Would be very useful to add this

            K Daniels added a comment -

            This is very much needed.  Please implement.

            K Daniels added a comment - This is very much needed.  Please implement.

            kanwarpreet singh added a comment -

            +1 This is much needed changes need to be done. Currently, there is no way to filter the issues by using custom fields like show the issues where custom field values changes before <this date> etc. 

            I am using Xporter add-on for the reporting purpose. Its an awesome tool to export the issues details as we want but its not capturing the history changes of the custom fields because JQL does not provide history search support to the custom fields. This is a limitation. Because of this, we are looking for other alternatives like script runner to create own custom fields and export the history changes but using tool like script runner would very difficult for the user who is not good enough in the javascript. I do vote for this change. 

            kanwarpreet singh added a comment - +1 This is much needed changes need to be done. Currently, there is no way to filter the issues by using custom fields like show the issues where custom field values changes before <this date> etc.  I am using Xporter add-on for the reporting purpose. Its an awesome tool to export the issues details as we want but its not capturing the history changes of the custom fields because JQL does not provide history search support to the custom fields. This is a limitation. Because of this, we are looking for other alternatives like script runner to create own custom fields and export the history changes but using tool like script runner would very difficult for the user who is not good enough in the javascript. I do vote for this change. 

            John Price added a comment -

            We would definitely like this.  We have a custom field that tracks a risk status (Red/Amber/Green) and would like to know when the status changed.  Please implement!

            John Price added a comment - We would definitely like this.  We have a custom field that tracks a risk status (Red/Amber/Green) and would like to know when the status changed.  Please implement!

            Matt Morrison added a comment -

            ++1 - this would be very helpful - bugzilla allows it

            Matt Morrison added a comment - ++1 - this would be very helpful - bugzilla allows it

            Nick Oman added a comment -

            +1

            Nick Oman added a comment - +1

            Anna Prostrollo added a comment -

            +1 

            Anna Prostrollo added a comment - +1 

              Unassigned Unassigned
              jspaniol Jeison
              Votes:
              189 Vote for this issue
              Watchers:
              101 Start watching this issue

                Created:
                Updated:
                Resolved: