i agree the current list of sling components in JIRA is very outdated and incomplete - and thus mostly not used.
on the other hand, using any single git repo name as component name will completely bloat this list, and probably make it unusable. ideally, we come up with a component list with each "related group of repos", e.g. one for all models-related repos, caconfig related repos etc. but this also comes with a downside - that list needs to be hand-curated, and maybe the its not obvious for everyone which repo belongs to which component. so, also considering that it can be automated, a component for each git repo might be a suitable compromise. stefan > -----Original Message----- > From: Carsten Ziegeler <[email protected]> > Sent: Tuesday, September 29, 2026 1:51 PM > To: [email protected] > Subject: [RT] Aligning Jira components with our git repos? > > 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]
