If an admin drag&drops the jira versions up/down in the correct order in that screen, then we could jql like: 'fixVersion >= 4.0 AND fixVersion < 5.0' and similar sorted/range queries which is quite handy when building up jql queries. My 2 cts.
On 4/1/21 9:18, Mick Semb Wever wrote: > For jira hygiene, the current precedence is that resolved tickets do not > keep their placeholder fixVersions. > For example, no resolved ticket should have a fixVersion of 3.0.x, 3.11.x, > 4.0-alpha, 4.0-beta, 4.0-rc, or 4.0.x. > > And… all 4.0-alphaX and 4.0-betaX resolved tickets should have the > additional fixVersion of "4.0". > (This was previously requested so that it was easier to search for any > tickets resolved leading to 4.0) > > With a little housekeeping over the holidays all existing jiras are > corrected, so this precedence should be a bit clearer now. > In addition the placeholder `4.0-alpha` fixVersion has now been archived as > it shouldn't be used or visible any longer. > > More info on placeholder fixVersions can be read here: > > https://issues.apache.org/jira/projects/CASSANDRA?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=unreleased > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
