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

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

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • None
    • 42
    • 4
    • Hide
      Atlassian Update – 8th February 2018

      Hi all,

      Thanks for your interest in this issue.

      While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We appreciate the benefits of such requests, but don't plan to work on this for the foreseeable future.

      This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.

      Best,
      Jira Server Product Managment

      Show
      Atlassian Update – 8th February 2018 Hi all, Thanks for your interest in this issue. While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We appreciate the benefits of such requests, but don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status. Best, Jira Server Product Managment
    • 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.

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

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

            Mike Joyce added a comment -

            Since this issue is already marked as  `Not Being Considered` and is linked to https://jira.atlassian.com/browse/JRASERVER-27641   which is open, would be good to move these comments there.

            Mike Joyce added a comment - Since this issue is already marked as  `Not Being Considered` and is linked to  https://jira.atlassian.com/browse/JRASERVER-27641    which is open, would be good to move these comments there.

            I'm also looking for this feature 

            Lwandile Rorwana added a comment - I'm also looking for this feature 

            Looking forward to this... 

            Prashanth Eb added a comment - Looking forward to this... 

            +1 this would be great

            Keegan Farley added a comment - +1 this would be great

            +1 looking fo this

            Omprakash Thamsetty added a comment - +1 looking fo this

            shagans added a comment -

            Agree that this would be helpful. it is difficult to drive some historical based metrics without this.

            shagans added a comment - Agree that this would be helpful. it is difficult to drive some historical based metrics without this.

            +1 very useful . Request for consideration in upcoming release. 

            Rajeev Ramaswamy added a comment - +1 very useful . Request for consideration in upcoming release. 

            topn0tch added a comment -

            Would be a very good functionality to have in Jira.

            topn0tch added a comment - Would be a very good functionality to have in Jira.

            +1 business impact
            -1 performance side

            Gonchik Tsymzhitov added a comment - +1 business impact -1 performance side

            +1, this is of great business impact . Please consider

            Jobin Mathew Joseph added a comment - +1, this is of great business impact . Please consider

              Unassigned Unassigned
              jspaniol Jeison
              Votes:
              409 Vote for this issue
              Watchers:
              200 Start watching this issue

                Created:
                Updated: