pagure

#1530 Option for users outside repository to add ticket metadata
Closed: Won't Fix by wombelix. Opened by jflory7.

Closed: Won't Fix
Reopen Issue

Summary

For some repositories, it would be helpful to allow members outside of a repository to select metadata for a ticket when they file, so to best categorize tickets by the person filing.

Analysis

This is something I noticed would be helpful for Pagure repos like the CommOps, Marketing, Diversity, and soon-to-be FAmNA Pagures. We have a few tags, milestones, and priorities set up for all of the repositories. To tag tickets with these metadata, you have to be added to the repository (which doing so grants access to read, write, and admin access for the repo).

An option (or maybe even just defaulting to this behavior) for users to select metadata when filing tickets would be helpful in these scenarios. Then, a repository owner can change and edit the metadata later if it is incorrect. But after being created, the ticket would not be able to edited by anyone outside of the repository.

Implementation

  1. User files new ticket.
  2. User is prompted to select metadata if they have not selected already when filing.
  3. User creates issue.
  4. User is unable to edit metadata.
  1. User files new ticket.
  2. User is prompted to select metadata if they have not selected already when filing.
  3. User creates issue.
  4. User is unable to edit metadata.

I'm thinking more of offering to enter some of the metadata in the page where
the issue is filled rather than a prompt.
Would that also be fine for you?

I'm thinking more of offering to enter some of the metadata in the page where the issue is filled rather than a prompt.
Would that also be fine for you?

Oh, sorry, I don't think I made this clear. I also envisioned the metadata being present on the page while filing the issue. The "prompt" would be given if they hadn't added / set any metadata when filing their ticket (maybe better words would be "alert box").

One possible extension to this could be adding a setting to allow an issue / PR assignee to update metadata and make state changes to an issue or PR (e.g. close or merge).

The last update was 4 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)
Metadata
None

RFE

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.