About the Affects Version field in Jira

[watery]

We usually run LTS, 14.10.13 actually.

Before upgrading I always monitor the release I’m planning to update to for regressions and issues that are being fixed in the release following that (i.e. I’m planning to update to 14.10.17, and check for things being closed in 14.10.18).

I’d like to ask what’s the usage of the Affects Version/s in Jira, e.g. in these cases::

• Possible SQL error in case of concurrent save of space
• Macros using RequireJS are not properly displayed by the standalone WYSIWYG editor even when JavaScript is enabled

These are two issues that have only 14.10.17 in that field: does it mean the bug has arised in that specific version, and previous versions are unaffected, or is it just the version it has been found or checked for existence?

[tmortagne]

@watery

just the version it has been found

I’m afraid it’s this one most of the time. Also, it implicitly includes any greater version until the “Fix Version/s”.

There is only for security issues that we are extra careful to put the very first version to be impacted.

[watery]

@tmortagne

I’m afraid it’s this one most of the time.

No problem, it is totally reasonable; it’s clear it would take a lot of effort checking them against every minor and patch version.