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

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • None
    • None
    • 21
    • 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.

    Description

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

      Attachments

        Issue Links

          is duplicated by

          Suggestion - JRASERVER-35898 Add support for historical searches to custom fields

          • Closed
          relates to

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

          • Closed

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

          • Gathering Interest
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Activity

            People

              Unassigned Unassigned
              jspaniol Jeison
              Votes:
              407 Vote for this issue
              Watchers:
              198 Start watching this issue

              Dates

                Created:
                Updated: