launchpad should have an option to clone a ticket, like bugzilla has

Bug #304812 reported by Fernando Miguel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Incomplete
Undecided
Unassigned

Bug Description

Some times, we need to take most of the data from a ticket to create a new one.
launchpad should have an option to clone a ticket, like bugzilla has.

Tags: lp-bugs
Revision history for this message
Eleanor Berger (intellectronica) wrote :

If at all, this is a Malone bug, not Launchpad.

Changed in launchpad:
status: New → Invalid
Revision history for this message
Eleanor Berger (intellectronica) wrote :

What would this be used for? I find it hard to believe that cloning bugs is a very useful feature. Bear in mind that the most important aspect of cloning, filing the same bug on several targets, is already handled quite elegantly by Launchpad.

Changed in malone:
status: New → Incomplete
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

I often clone bug reports in Gnome Bugzilla to report several bugs about the same window, where the text I'm duplicating describes (a) what version and OS I'm using and (b) steps to access the window in question. Where I do the equivalent in Launchpad I just copy and paste, though sometimes I forget to copy before clicking the "Report another bug" link, so I have to go Back Copy Forward.

Revision history for this message
Graham Binns (gmb) wrote : Re: [Bug 304812] Re: launchpad should have an option to clone a ticket, like bugzilla has

Another application for this would be for people who want to clone not
a whole bug but part of a bug. Consider this use case:

1) The foo project has a bug filed against it which is a security bug
and is therefore automatically private
2) The developers of foo realise that the bug is partly in their code
but also partly in an upstream library to which their code links. The
upstream code isn't a security concern, but fixing that bug would help
to fix the security bug in foo.
3) The developers then clone the security bug, remove all the
foo-specific and security-specific information from it and target it
to the upstream project. All the data from the original bug report was
available when they created the new one, so it was simply a case of
excising the bits that didn't apply or were need-to-know.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.