-
Suggestion
-
Resolution: Duplicate
-
None
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
It would be good to have support for historical searches such as WAS for custom fields. This would enable queries such as:
sprint was in ("sprint1") and sprint in ("sprint2")
- duplicates
-
JRACLOUD-34103 Ability to use operator WAS / WAS IN / WAS NOT / WAS NOT IN in custom fields
- Closed
- is related to
-
JRASERVER-35898 Add support for historical searches to custom fields
- Closed
[JRACLOUD-35898] Add support for historical searches to custom fields
Workflow | Original: JAC Suggestion Workflow [ 3147716 ] | New: JAC Suggestion Workflow 3 [ 3652633 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2342396 ] | New: JAC Suggestion Workflow [ 3147716 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2104714 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2342396 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2067484 ] | New: JIRA Bug Workflow w Kanban v6 [ 2104714 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 1840808 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2067484 ] |
Description |
Original:
It would be good to have support for historical searches such as WAS for custom fields. This would enable queries such as: {code}sprint was in ("sprint1") and sprint in ("sprint2"){code} |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-35898]. {panel} It would be good to have support for historical searches such as WAS for custom fields. This would enable queries such as: {code}sprint was in ("sprint1") and sprint in ("sprint2"){code} |
Link |
New:
This issue is related to |
Project Import | New: Sat Apr 01 19:36:47 UTC 2017 [ 1491075407146 ] |