Some use the version field, some the components field, some do not care,
some use both.
Nothing is ideal - we discussed this yesterday at the Sling Community
Roundtable at adaptTo and there are some interesting alternative
proposals, so stay tuned for a new discussion around that topic coming
up soon.
Regards
Carsten
On 9/29/2026 3:17 PM, Jörg Hoh via dev wrote:
I wonder if anyone of us is really using the Jira components.
I personally mostly rely on the "affected version" field to understand
which codebase needs to be looked at. Do we have automation/processes which
would benefit from such an effort?
Jörg
Am Di., 29. Sept. 2026 um 13:51 Uhr schrieb Carsten Ziegeler <
[email protected]>:
Hi,
for the most important modules (git repos) we have a separate component
in jira, like api, engine etc.
But that is not consistent.
I suggest we make an effort to align those, every git repo getting a
separate component, removing components which are not based on a git repo.
This would make issue handling easier, especially when
triaging/evaluation issues.
WDYT?
Carsten
--
Carsten Ziegeler
Adobe
[email protected]
--
Carsten Ziegeler
Adobe
[email protected]