Hey, well we have this mapping already in repo-metadata and project-api ;) look here:
https://projects.kde.org/api/v1/identifier/kmail repo-metadata see bugzilla entry for each repo: https://invent.kde.org/sysadmin/repo-metadata/-/blob/master/projects-invent/ pim/kmail/metadata.yaml The propper solution would either use either repo-metadata or project-api to get the needed bugzilla products. You may also add the metadata first to the repo, if KMail is more or less the only exception, it should be easy ;) I can update the metadata, if someone can tell me how to get a list of all repos inside KDE Gear and I'll also check if this bugzilla urls are really valid... If the add versions to bugzilla is a python script I can also help there to implement an solution with repo-metadata or projects-api. > To my knowledge, KMail is the only project/product that uses a Bugzilla > product name that is different from the repository name. > It is therefore the sole exception to that rule. There are also some repos that are bundeled together into one product, but as the main product has also its own repo, that's why it wasn't noticed yet. e.g. * akonadi-search -> product: akonadi, component: indexer * akonadiconsole -> product: akonadi, component: akonadiconsole well there are some other exceptions in frameworks (instead of frameworks- <product>): * extra-cmake-modules -> component: extra-cmake-modules * breeze-icons -> product: breeze, component: icons * oxygen-icons -> product: oxygen, component: icons * plasma-frameworks -> product: frameworks-plasma Regards, hefee
