You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
I would like to ask a question on the affectedVersion field usage in the JQL search. Are these JQL searches are based on the created date of the Release Version in the Release section or is it based on the internal release ID?
I have "Release A" "Release B" "Release Aa" "Release C" versions created in the Release section in the order mentioned before. The "Release Aa" is a dependent or we can call it as a maintenance release of "Release A". And my JQL is trying to fetch the Issues <= "Release B". Which mean that the issues with affectedVersions having values "Release A" "Release B" "Release Aa" should be listed. At this point for me, the issues having affectedVersion "Release Aa" are not listed.
JQL: affectedVersion <= "Release B"
Hence the question here is, are the search results are based on the release Created date in Jira or the internal ID associated with the Version?
Please let me know if I have to provide any other details. Looking forward for a quick response from the Atlassian or Community experts.
Thanks in advance!!
It's base on the order the version or in the version list in the project admin section.
- The comparison operators (e.g. ">") use the version order that has been set up by your project administrator, not a numeric or alphabetic order.
The version on top is considered after the one below.