Created attachment 2140064 [details] Screenshot of kernel component's custom issue report template Hi, GNOME SIG is currently using a Bugzilla Rules Engine rule https://bugzilla.redhat.com/page.cgi?id=ruleengine%2Fdetails%2Findex.html&rule_name=Further%20Upstream%20First%3A%20GNOME to add comments to issue reports after they are created. FESCo has requested that we explore whether it would be possible to replace the automatic comments with an issue report template, which would allow users to view our message *before* creating a bug report, rather than after. The Fedora/kernel component already has its own custom issue report template (screenshot of this attached) so I hope we can do something similar. We would like to apply the issue report template to all packages where Assignee is: @gnome-sig. If it's possible to set the template based on assignee instead of particular components, that would be ideal, because we'll likely change many more Assignees to @gnome-sig in the future, possibly frequently, and it would be nice to not need to create a new bug report here each time we want to add more packages to the template. But I assume that's probably not possible? If not, then let's set it to the following list of components, and we'll just create a new bug report here whenever we want to add more components: The current packages with assignees set to @gnome-sig is: bijiben evince foundry gjs gnome-bluetooth gnome-calendar gnome-clocks gnome-connections gnome-contacts gnome-control-center gnome-disk-utility gnome-initial-setup gnome-manuals gnome-music gnome-online-accounts gnome-session gnome-settings-daemon gnome-shell gnome-user-share gtk3 gtk4 gvfs libcloudproviders libgexiv2 loupe mutter nautilus pygobject3 seahorse showtime snapshot totem totem-pl-parser The desired custom template text is: Please consider reporting your issue directly to GNOME at https://gitlab.gnome.org/GNOME/ to improve the chances that your issue will be resolved. Create bug reports here only if (a) the bug relates to Fedora packaging or integration with other Fedora components, or (b) a Fedora bug report is required for Fedora release processes, such as blocker bugs and freeze exceptions. Otherwise, please report your issue on GNOME GitLab instead. Thank you!
Hi, the Fedora Kernel has it's own BugViewPlus template. These templates are set on components and completely replace the text in the default description when creating bugs on those components. So we'de create one new BVP template and apply it to multiple components. Note that while it's fine to advise the user to use a different system, the text should contain all the text they should use if the decide not to do that.
Note that while only RHBZ admins can create or edit the BVP templates, anyone in the fedora_pm group can set the template used on a component. This is done using the "Default description" drop down on the component edit page.
This sounds good. I'm sure can figure out who is in fedora_pm group and ask them when we need to apply the template to new components. (In reply to Jeff Fearn 🐞 from comment #1) > Note that while it's fine to advise the user to use a different system, the > text should contain all the text they should use if the decide not to do > that. I don't think we actually need anything more than the message. The usual Fedora issue report template is pretty rigid and not really needed IMO.
Please let me know when the new BVP template is ready. Then I'll ask fedora_pm folks to apply it to our desired components.
Hi, this is in place. Name: gnome-sig, description: Gnome Sig Template, ID: 121.