Bug 909480
| Summary: | Automatically create "cloned" bugs in "Layered Product Common for RHEL 6" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Debi Rieden <drieden> | ||||
| Component: | python-bugzilla | Assignee: | Will Woods <wwoods> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | bugs.michael, crobinso, dzickus, jpokorny, jskarvad, mcermak, mpetlan, pschiffe, snagar, wwoods | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-04-15 05:03:17 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: | |||||||
| Attachments: |
|
||||||
|
Description
Debi Rieden
2013-02-08 21:34:46 UTC
(In reply to comment #0) > I have a need, not sure if it is possible. If you can do this, it would > really cut down on mistakes and eliminate bugs not being created for issues > found. > > Question: > Is there a way to automatically create a bug (clone) based on an existing > bug? > The cloning would be done without human intervention. > > Please let me know if this is possible and what I need to do. This is not possible in Red Hat Bugzilla. It would be my recommendation that you create a script that gets newly created bugs, and 'clones' them[1]. Both of these things can be done via RPC calls to Red Hat Bugzilla. -- simon [1] By 'clone', I mean create a new bug. I recently attempted to put the bug cloning functionality into bugzilla or at least into python-bugzilla package: https://bugzilla.redhat.com/show_bug.cgi?id=923436 https://bugzilla.mozilla.org/show_bug.cgi?id=860623 I have a patch in hand for this. Upstream don't want it, and I don't want it in our Bugzilla for the same reason. I'm reassigning this bug to python-bugzilla. Feel free to attach the patch to this bug, as see if they will pick it up. I'm not really interested in maintaining this in python-bugzilla either, since it sounds like a maintenance nightmare since clone behavior may change across bugzilla versions. I'd recommend just publishing a 'clone' script built around python-bugzilla and point interested users at that. This way the maintenance nightmare moves from {python-,}bugzilla to user scripts. But that it life ;-) Understood. Thanks.
Created attachment 827050 [details]
proposed patch
Since I was privately asked for the patch, I'm attaching it here.
On 19 March, 2013 the patch was rebased against upstream source
(git clone git://git.fedorahosted.org/git/python-bugzilla.git)
and internal tests 'python setup.py test' and 'python setup.py pylint'
didn't regress.
|