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

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • None
    • Component/s: None
    • None
    • 42
    • 12
    • 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

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

            Assignee:
            Unassigned
            Reporter:
            Jeison (Inactive)
            Votes:
            410 Vote for this issue
            Watchers:
            201 Start watching this issue

              Created:
              Updated: