#968 Adding e-mail addresses to Cc at tickets (without creating a pagure account)
Closed: Won't Fix a year ago by wombelix. Opened 7 years ago by robert.

As of writing, the Fedora Free Media Program allows to create anonymous and private trac tickets, which are being handled by free media group members. The disadvantage with trac is, that the requester needs to use "reply all" when replying via e-mail (to update/answer the ticket).

At pagure it's not possible to create tickets without an account, neither via API nor via git (last of it creates an account). Given the account is public, this might not be what free media requesters are expecting on one hand, on the other hand this might be about 30.000+ accounts after 5+ years or so (based on current trac).

Thus the idea could be to create the ticket via the pagure API with a defined user, however with adding the e-mail address of the requester to Cc at this ticket - but without creating a pagure account. As it was pointed out, this is a potential spam scenario (add somebody to all tickets and the person can't do anything against). One idea was to make that feature optionally per project via admins, but there might be other options as well.

While the ticket focuses adding e-mail addresses to Cc at tickets (without creating a pagure account), related ideas and suggestions are also welcome.


This feature is more in line with a ticket tracker than what we are trying to implement in Pagure, which is a bug tracker.

IMHO, this is a feature that is a little out of scope for Pagure.

This feature is more in line with a ticket tracker than what we are trying to implement in Pagure, which is a bug tracker.

IMHO, this is a feature that is a little out of scope for Pagure.

I know that pagure is not completely suitable here, however I got the impression that everything should be migrated sooner or later from Fedora Hosted to Pagure if somehow possible. Alternatively, Fedora Infrastructure would maybe have to maintain another application.

The last update was 6 years ago, no further requests, updates or actionable tasks since then, I'm going to close this issue for now to reduce our backlog.

Metadata Update from @wombelix:
- Issue close_status updated to: Won't Fix
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata