Bug 2213800

Summary:	Template for kernel bug reports is broken in bugzilla
Product:	[Community] Bugzilla	Reporter:	Christopher Klooz <py0xc3>
Component:	Creating/Changing Bugs	Assignee:	Jeff Fearn 🐞 <jfearn>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jeff Fearn 🐞 <jfearn>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.0	CC:	kevin, py0xc3
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.0.4.RH89	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-03 00:13:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Christopher Klooz 2023-06-09 12:42:28 UTC

Description of problem:
In the past, when users have filed a bug against the component kernel in the product Fedora, they were provided with a template that informed them about what information they shall provide (e.g., dmesg).

This template was added to the bug report once the component "kernel" was chosen.

Now, the template seems to be broken. I became aware when I saw increasingly users to file bug reports against kernel without providing the data that used to be asked for in the template.

Also see https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/JT5CNONS4K4DMZCVMEN6C3KIRFQVEHNI/

Version-Release number of selected component (if applicable):
Current bugzilla, product Fedora, component kernel

How reproducible:
Always

Steps to Reproduce:
1. File a bug against kernel

Actual results:
Once the component "kernel" has been chosen, the report remains blank without template.

Expected results:
Once the component "kernel" has been chosen, the remaining report should be filled with a template, which triggers the user to an appropriate bug report.

Additional info:
/

Comment 1 Jeff Fearn 🐞 2023-06-13 00:08:19 UTC

The template is still there and works if you use the unguided form.

e.g. 
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=kernel&format

Need to look in to how to use the per component templates on the guided 
form, or we might need to redirect to the unguided form if it's too hard.

Comment 2 Christopher Klooz 2023-06-13 12:50:24 UTC

The issue I see is that those who would need the template are those who are not aware of the unguided form. They just click through the buttons and end up on the guided form. So redirecting would be a good interim solution imho, maybe even a permanent one (in my subjective perception the unguided one looks more intuitive anyway).

Comment 3 Jeff Fearn 🐞 2023-07-28 04:28:24 UTC

On QA server:

1. Enter create bug page for fedora product

Guided entry page is loaded with the separated text entry boxes.

2. Select kernel component

All separated text entry boxes aside from the Details etxt box are hidden The Details text box displays the kernel template.

3. Enter required data and submit.

A bug is created using the kernel template.

4. Create another bug using a component that uses the default template.

Bug is created with description as expected.

5. Follow a link to the bug creation page with the kernel as a parameter.

enter_bug.cgi?product=Fedora&component=kernel

Bug creation page loads with kernel template loaded and other separated text entry boxes hidden.

6. Enter required data and submit.

A bug is created using the kernel template.

7. Enter create bug page for fedora product, switch components between ones that use the default template and a custom template.

Fields are hidden and shown as expected and but templates are loaded and cleared as expected.

Comment 4 Jeff Fearn 🐞 2023-07-29 01:54:26 UTC

This fix has been deployed to stage Bugzilla for a short public testing phase.

https://bugzilla.stage.redhat.com

Comment 5 Jeff Fearn 🐞 2023-08-03 00:13:45 UTC

This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.