-
Suggestion
-
Resolution: Duplicate
-
None
When a version is published it is possible to specifiy if the "fixed for version" of the issues should be kept or changed transfered to another version.
Is there a posibilty to integate the adaption of filters which refere to the "fixed for version?
Otherwise these filters have to be adapted manualy each time a version is published.
I am aware that changing filters of other users could be a problem.
Maybe someone has another solution how to handle filtering for the [next | next++ | next+2] version?
- duplicates
-
JRASERVER-1357 Allow filter by "Next Unreleased Version"
- Closed
[JRASERVER-14535] Adapt filters which refer to a specific version when this version is released.
Workflow | Original: JAC Suggestion Workflow [ 3050048 ] | New: JAC Suggestion Workflow 3 [ 3675705 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2610865 ] | New: JAC Suggestion Workflow [ 3050048 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2569696 ] | New: Confluence Workflow - Public Facing v4 [ 2610865 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2335430 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2569696 ] |
Labels | Original: affects-server publishing | New: affects-server |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2113515 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2335430 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2074082 ] | New: JIRA Bug Workflow w Kanban v6 [ 2113515 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 887026 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2074082 ] |
Labels | Original: publishing | New: affects-server publishing |
Component/s | New: Project - Releases [ 43396 ] | |
Component/s | Original: Filtering & Indexing [Deprecated] [ 10231 ] |