Bug 213915
| Summary: | RFE: Add "file bug on this product/component" link to show_bug.cgi | ||
|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | Zack Cerza <zcerza> |
| Component: | Creating/Changing Bugs | Assignee: | Jeff Fearn 🐞 <jfearn> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.6 | CC: | mcepl |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-07-19 04:53:40 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Zack Cerza
2006-11-03 19:02:53 UTC
comment in fedora-devel ML today On 2008-11-19, 21:49 GMT, Seth Vidal wrote: > If you know the package where you think the bug is you can use > bugz:) > > http://bugz.fedoraproject.org/$name > > for example > http://bugz.fedoraproject.org/yum/ Looks good! And especially that it has solution for https://bugzilla.redhat.com/show_bug.cgi?id=213915 That's great and it helps for Fedora, but I wouldn't call it a solution as it won't work for anything else in this bugzilla, e.g. RHEL. *** Bug 486230 has been marked as a duplicate of this bug. *** Red Hat Bugzilla is now using version 3.4 of the Bugzilla codebase and therefore this feature will need to be implemented against the new release. Updating bug version to 3.2. This is very much alive as well. Red Hat has now upgraded to Bugzilla 3.6 and this bug will now be reassigned to that version. It would be helpful to the Bugzilla Development Team if this bug is verified to still be an issue with the latest version. If it is no longer an issue, then feel free to close, otherwise please comment that it is still a problem and we will try to address the issue as soon as we can. Thanks Bugzilla Development Team live and kicking Just to be sure it is not a suitable workaround, how about using the "Clone this bug" link in the top right of show_bug.cgi? Only bad thing is it also pulls in all of the comments, summary, and other things that would need to be edited. Or is it that you are asking for a clear bug that already has the product/version set? Dave No, cloning won't work very well for the reasons you mention. The other option is what this report is asking for. As part of the recent Bugzilla 4.2 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time. If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically. Thanks, the Bugzilla team. As part of the recent Bugzilla 2.4 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time. If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically. Thanks, the Bugzilla team. This link exists at the bottom of the search results page. |