-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
None
-
12
-
4
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
There should be the possibility to allow JQL requests for versions.
Therefore, why not just consider versions as parent issues? (or anything else)
They would be "invisible" in default filters but users could eventually select a type of filter like : "issues" or "versions" in the basic filter...
This is a suggestion, please vote, improve and detail it if you like the idea.
Otherwise for a workaround :
As versions cannot be filtered, it'd be interesting to have the possibility to trigger the automatic creation of a new issue every time the "release" button is pressed.
- is related to
-
JRASERVER-25390 In the issue navigator, component field should support the operator '~'
- Needs Triage
-
JRASERVER-10692 Possibility to search issues for NON ARCHIVED or ARCHIVED versions
- Gathering Interest
-
JRASERVER-14588 Implement Component and Version Schemes
- Gathering Interest
-
JSWSERVER-9237 Multiple versions in version report
- Gathering Interest
-
JSWSERVER-13595 Limit Scrum Board Versions sidebar to only versions returned by the board's JQL filter.
- Gathering Interest
- relates to
-
JRACLOUD-64868 Make Versions' fields accessible for JQL filtering
- Closed
-
JRASERVER-29717 As a user, I would like to be able to use a wildcard on fields like components, versions, assignees, etc
- Closed
-
JRASERVER-19775 Allow ~ Operator for fixVersion field
- Gathering Interest