Details
-
Suggestion
-
Resolution: Duplicate
-
None
-
None
-
None
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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
- duplicates
-
JRASERVER-45522 JQL function that Allows you query what status an issue was in at a particular time.
- Closed
-
JRASERVER-61373 Implement the "WAS" operator for the issue type JQL Search
- Gathering Interest
- relates to
-
JRACLOUD-60707 Add 'was' operator to issuetype for JQL search
- Closed