Description
Expressions like fixVersion > A AND fixVersion < B work as expected when an issue has just one Fix version. When there are multiple Fix versions the above expression is interpreted as "has value > A AND has (another) value < B".
This causes quite a bit of a confusion - see JRASERVER-22995.
It would be useful to be able to specify a "has value between A AND B" kind of condition.
Possible syntax could be as following: fixVersion BETWEEN A AND B or fixVersion IN (A - B).
Here is the full story.
Our project has several components with their own release cycles. So there are versions like 'UI-1.0.13' and 'DL-1.7.0'.
Occasionally we make a "product release" that includes specific versions of the components: 'R1', 'R2', etc.
Product releases are "rolling". I.e. individual components could be updated later and "delivered" into 'R1'.
I would like to be able to filter JIRA issues to see which fixes were delivered in 'Rn' release. And would prefer not having to add a label or an extra 'R1' fix version to every issue.
Some components are quite tightly coupled with the releases. I.e. R2 will likely have 'UI-2.0.x' versions.
Others are pretty independent. So R2 would have DL-1.7.3 and R3 will use DL-1.7.4
So using regexp patterns as suggested in JRASERVER-22995 would not quite work.
My idea was to create "marker" versions for product releases: R1, R2, etc.
And make sure all the components versions are sorted properly with relation to product versions.
And then a query like "fixVersion between R1 and R2" would easily show me all the changes delivered in the R2 release.
Other options I could think of are:
- Provide hierarchical versions (at least 1 level deep) and turn all component versions into corresponding product versions children; then filter as fixVersion IN R1.
- Implement tags for versions and then filter (quite indirectly) based on something like fixVersion.tag = R1
I would appreciate if you could suggest a better way to address this.
But nevertheless I think having "value in range" type of condition would still be useful for JQL.
P.S. It would be great if you could backport this change to JIRA version 7.5.x
