On Wed, 2026-03-04 at 13:08 -0500, Stephen Gallagher wrote: > In the case of integration projects (like Fedora) where we have to > interact with MANY different projects, Neal makes an excellent point: > right now, we have a single tracker whose links are stable: if I file > a bug against Node.js and it turns out it's actually caused by a bug > in the libuv platform library or even a code-generation bug in gcc, > the same ticket ID and URL will continue to get me to that bug, > regardless of reassignment by component. With a Forgejo-centric ticket > tracker, we'd have to keep re-filing the tickets across whatever > project we *think* is the right place for it (and maintain backwards > and forwards links there). It makes it really hard for the original > submitter of the issue to keep track of it.
GNOME has implemented moving tickets on Gitlab, somehow or other. We could presumably do the same on Forgejo. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @[email protected] https://www.happyassassin.net -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
