Bugs are being reported on the Component Version for the Affects Version/s and Fix Version/s fields.
Each Component Version belongs to one-or-many Bundles.
We expect that if we want to search for the Bugs that are fixed between Bundle Versions that we can use the Fixed In Bundle field in combination with the betweenVersions JQL function, however this doesn't return any issues as expected.
there is a Bundle A with version "Bundle A, Version 1.0.0"
there is a Bundle A with version "Bundle A, Version 20.0.0"
there is a component version, with version "component, 2.0.0"
component version belongs to some Bundle between versions 1.0.0 and 20.0.0 above
an issue is fixed with fix version "component 2.0.0" (but not explicitly also it's Bundle version)
Then this JQL statement should return that issue:
project = SOMEKEY and "Fixed In Bundle CustomField" in betweenVersions("Bundle A, Version 1.0.0","Bundle A, Version 20.0.0")
Actual result is no issues returned.
If you use "Product A - 1.2.3" instead of "Product A, 1.2.3" it should work without manually defining version relationships.
Huh…What about “Product A - 1.2.3” if the actual version name is “Product A, 1.2.3 (Customer-Facing Nickname)”? Is it able to extract the semantic version in that case as well?
Does it also support other aspects of SemVer 2.0 such as tags and prereleases? (1.2.3-12+a12b3c)
Unfortunately it only supports '-' at the moment. I wan't aware of tags and prereleases in semantic versioning. So it only supports #.#.# format. I have created to support other characters.
You can use something like "Affects Bundle" in betweenBundles("SSM Release 1", "SSM Release 3") in version 1.14.1.