Learn more about these different git repos.
Other Git URLs
In Trac, there were "components", and people filing new tickets could set up which component this ticket is related to, e.g. Test Days. In Pagure, there's nothing like that. There are tags, but those have to be assigned manually by the project owners after the ticket is created, the reporter can't modify them.
Test Days
I see 2 options how to improve this:
a) Allow reporters to assign some tags initially, when creating the ticket. That will allow reporters to set useful tags like Test Days (category), or Bug/RFE. It should be possible to pre-fill those from URL, as requested in #1860. This should be only possible when creating the ticket - after creation, only the project owners should have the right to change tags. Alternatively, this all can be configurable - there can be toggles in project options whether reporters can assign tags when creating tickets, and whether they can further adjust them after the ticket is created.
Bug
RFE
b) Only allow to set tags from the URL, but not manually. This will allow us to create tailored hyperlinks (e.g. Create a Test Day ticket with https://pagure.io/fedora-qa/new_issue?tags=testday link), but it will not give the user free hands to set whatever they want (they still can edit the URL, so it's not a hard obstacle, but most people won't).
Create a Test Day ticket
Relates to https://pagure.io/pagure/issue/926
Metadata Update from @pingou: - Issue tagged with: RFE
Metadata Update from @vivekanand1101: - Issue assigned to vivekanand1101
I think this relates to https://pagure.io/pagure/issue/926 (because if we do a, doing b is trivial), so I have the tendency to think this is a duplicate
The only difference that i see a project level conf key being asked in (a) . For me this is unnecessary because, if a user is allowed to change tags/assignees he may as well do that in the very beginning. And, if he is not, he shouldn't be able to do that via URL as well.
Metadata Update from @vivekanand1101: - Assignee reset
The last update was 5 years ago, no further requests, updates or actionable tasks since then. Related Issues are marked as fixed. 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)
This is even duable now if the person opening the ticket has the permission to set tags on the project.
Login to comment on this ticket.