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

Add 'was' operator to issuetype for JQL search

    XMLWordPrintable

Details

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

    Description

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

      Problem Definition

      Based on this document: https://confluence.atlassian.com/jira/advanced-searching-179442050.html#AdvancedSearching-Type

      'was' is not a valid operator for issuetype

      Suggested Solution

      Add 'was' operator for issue type as this would allow reporting on past issue types.

      Workaround

      Using the the JIRA Suite Utilities plugin it's possible to use the Copy Value From Other Field Post-Function, allowing JIRA to be setup in the following manner:

      Remove the Issue Type field from the default screen scheme, disabling users ability to edit an issue type normally.
      Add a workflow step to change the issue type.
      This step will use the JIRA Suite Utilities post-function to set the old Issue Type in the Custom Field.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              b9398446e1b3 David Perez
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: