Bug 1731835
| Summary: | New Bugzilla template for Fedora nonresponsive policy | ||
|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | Miro Hrončok <mhroncok> |
| Component: | Bugzilla General | Assignee: | Jeff Fearn 🐞 <jfearn> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Lianghui Yu <liyu> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.0 | CC: | bzhang, igor.raits, jfearn, kevin, liyu, qgong, zbyszek |
| Target Milestone: | 5.0-RH7 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 5.0.4-rh29 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-09-10 22:20:06 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
Miro Hrončok
2019-07-22 07:36:34 UTC
Hi, you cannot have a component of none. There are two options that look reasonable. 1: Place a component widget on the page and let the user select the component in questioned. 2: Have a dedicated component for this process. #2 has the positive effect that this could then be done as a bug template and could be done right away instead of shipping in a package update as is required for creation templates. e.g. https://beta-bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=Unresponsive%20Maintainer If you go for #2 you might consider if it's better to put it in another product, since there are ~30K components on Fedora so thing can be hard to find . Another consideration is that if you are sending people to this URL from a Fedora site then you might consider supplying the summary, component & comment template in the URL. Probably more useful if you want the bugs opened against the "real" components. e.g. https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=publican&comment=Dear%20jfearn,%20please%20stop%20being%20slack%20on%20publican!&short_desc=Nonresponsive%20maintainer%20check%20for%20jfearn Finally you might consider using a flag, targeted at the user in question. The next release will reintroduce the regular nag mail about pending flag requests. This might give a user more opportunities to respond to the request than a bug would. I'd say: 1) Place a component widget on the page and let the user select the component in questioned. +1 for 1).
> If you go for #2 you might consider if it's better to put it in another product, since there are ~30K components on Fedora so thing can be hard to find .
That's a problem, but so far, everything in Fedora is using this one "product", including Package Reviews,
so I think it's best to stick to the same setup here.
After discussion, we realized that we need the same process to work for modules and containers. I.e. something like: https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora Modules&format=fedora-nonresponsive-maintainer and https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora Container Images&format=fedora-nonresponsive-maintainer The only difference between the template would be that <package> is replaced by <module> or <container> as appropriate. Jeff, what are the URLs for the new templates? (In reply to Zbigniew Jędrzejewski-Szmek from comment #5) > Jeff, what are the URLs for the new templates? Currently they are only accessible internal to Red Hat, once they have passed QE I'll push them out to beta-bugzilla and update here with some links. Okay Verified on latest QE environment, https://[bugzilla url]/enter_bug.cgi?product=[any fedora product]=fedora-nonresponsive-maintainer Will work and able to file a bug. Result: PASS https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&format=fedora-nonresponsive-maintainer returns > file error - cannot find file - bug/create/create-fedora-nonresponsive-maintainer.html.tmpl () ? (In reply to Zbigniew Jędrzejewski-Szmek from comment #8) > https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&format=fedora- > nonresponsive-maintainer > returns > > file error - cannot find file - bug/create/create-fedora-nonresponsive-maintainer.html.tmpl () > > ? As per comment #1, if you use this method for making changes then you need to wait for a release before you can get stuff in production. This won't be available on production until sometime after the status is changed to "RELEASE_PENDING". That is likely to be in 2-3 weeks from now. FYI this is now deployed to beta-bugzilla. https://beta-bugzilla.redhat.com/enter_bug.cgi?product=Fedora&format=fedora-nonresponsive-maintainer https://beta-bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20Container%20Images&format=fedora-nonresponsive-maintainer https://beta-bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20Modules&format=fedora-nonresponsive-maintainer This change has been deployed to the pre-production infrastructure at https://partner-bugzilla.redhat.com Seems that this has been deployed. https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&format=fedora-nonresponsive-maintainer https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20Container%20Images&format=fedora-nonresponsive-maintainer https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20Modules&format=fedora-nonresponsive-maintainer Thanks. 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. |