Requirements and Investigation Ticket Tracker for Fedora's Bugzilla Replacement #3664

New issue

Open

opened 2026-07-29 16:52:01 +00:00 by amoloney · 4 comments

amoloney commented

2026-07-29 16:52:01 +00:00

Owner

Fedora will need to identify a suitable replacement for Bugzilla. This ticket will serve as a high-level tracker for the progression of this work.with thi

The overall owners of this change will be FESCo, and the FOA and CLE Product Owner will work with this group to begin scoping requirements for major users of bugzilla. This is likely to include, but not limited to packagers, Fedora QA, change wrangler, and other users.

Fedora Council is expected to be kept informed of this effort via the FESCo rep, and will offer their support or guidance when needed.

A timeline for this requirements gathering and overall approx timeline for the migration will follow.

Fedora will need to identify a suitable replacement for Bugzilla. This ticket will serve as a high-level tracker for the progression of this work.with thi The overall owners of this change will be FESCo, and the FOA and CLE Product Owner will work with this group to begin scoping requirements for major users of bugzilla. This is likely to include, but not limited to packagers, Fedora QA, change wrangler, and other users. Fedora Council is expected to be kept informed of this effort via the FESCo rep, and will offer their support or guidance when needed. A timeline for this requirements gathering and overall approx timeline for the migration will follow.

❤️ 2

gotmax23 commented

2026-07-29 16:55:12 +00:00

Owner

Ref: https://fedoraproject.org/wiki/Infrastructure_Fedora_bug_tracker

gotmax23 referenced this issue from council/tickets

2026-08-04 01:25:22 +00:00

Proposed Private Issues Process for Fedora Forge #577

t0xic0der referenced this issue from council/tickets

2026-08-04 03:06:27 +00:00

Proposed Private Issues Process for Fedora Forge #577

decathorpe commented

2026-08-04 14:36:53 +00:00

Owner

This topic is on the agenda for today's meeting:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/PWMQRM2RQXWIGSQQPX643JE3ADM5Y3AC/

This topic is on the agenda for today's meeting: <https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/PWMQRM2RQXWIGSQQPX643JE3ADM5Y3AC/>

decathorpe commented

2026-08-04 18:17:27 +00:00

Owner

This was discussed during today's meeting (meeting log starting at 17:21:05). We agreed on two action items:

@decathorpe to set up a ticket tracker that will be used for gathering workflows ("~~user stories~~") from any groups that currently use bugzilla (which is, essentially, all of them) and start sending out requests for those requirements.
@decathorpe to send an announcement email with more information and context to the devel / devel-announce mailing list.

I'll mark this ticket as "stalled" for now since it is no longer immediately actionable, and will only become actionable again when the requirements gathering phase ends and the discussion period starts.

This was discussed during today's meeting ([meeting log](https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-08-04/fesco.2026-08-04-17.00.log.html) starting at 17:21:05). We agreed on two action items: - @decathorpe to set up a ticket tracker that will be used for gathering workflows (*"~user stories~"*) from any groups that currently use bugzilla (which is, essentially, *all* of them) and start sending out requests for those requirements. - @decathorpe to send an announcement email with more information and context to the devel / devel-announce mailing list. I'll mark this ticket as "stalled" for now since it is no longer immediately actionable, and will only become actionable again when the requirements gathering phase ends and the discussion period starts.

decathorpe added the

stalled

label

2026-08-04 18:17:37 +00:00

decathorpe self-assigned this

2026-08-04 18:17:39 +00:00

decathorpe commented

2026-08-06 19:21:54 +00:00

Owner

The ticket tracker is now set up (including a short README and a default ticket template):
https://forge.fedoraproject.org/fesco/rhbz-replacement-requirements

I also sent an email to devel-announce, which still needs to be ack'd as it got moderated.

The ticket tracker is now set up (including a short README and a default ticket template): <https://forge.fedoraproject.org/fesco/rhbz-replacement-requirements> I also sent an email to devel-announce, which still needs to be ack'd as it got moderated.