allow attaching previously uploaded blobs (apport-style) to existing bugs

Bug #85040 reported by Martin Pitt
36
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
High
Unassigned

Bug Description

This idea came up at:

  https://lists.ubuntu.com/archives/ubuntu-devel/2007-February/023282.html

It would be helpful if we could attach a MIME/Multipart blob to an already existing bug report, similar to what is happening with filing new bugs.

Opening .../bugs/12345?addblob=<token> (or similar) would bring up a message that additional information is attached to the bug and allow the user to add some additional comments (but it shuold be pointed out that this is entirely optional). When he clicks 'submit', the blob would be broken into new bug attachments, and the comment added to the bug trail.

Changed in malone:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Joey Stanford (joey) wrote :

raising to high as it also affect distro

Changed in malone:
importance: Medium → High
Changed in malone:
milestone: 1.1.11 → 1.2.2
Changed in malone:
assignee: nobody → allenap
Changed in malone:
milestone: 1.2.2 → 1.2.4
Changed in malone:
milestone: 1.2.4 → 1.2.6
Revision history for this message
Scott Beamer (angrykeyboarder) wrote :

I don't know if this belongs here or in a seperate bug report, but I'd like to be able to attach everything apport has collected on an app crash to an existing bug report.

I often find a bug that is the same as what I'm experience, so I don't file a dupe, but the original report is often incomplete and I've got stack traces, core dumps and soforth reeady to attach but apport on;y seems to be intersted in doing that with a brand new bug report.

It seems kind of a waste not to be able to add (very) useful information to an existing report with a tool that Ubuntu provides to add such information to new reports.

Revision history for this message
Björn Tillenius (bjornt) wrote :

Untargeting this for now to help with planning. Will retarget it later.

Changed in malone:
milestone: 1.2.6 → none
Revision history for this message
Martin Pitt (pitti) wrote :

With python-launchpad-bugs or launchpadlib we can actually implement this on the client side, by uploading every attachment individually; doesn't look as nice (all attachments in a single comment), but certainly sufficient for this use case.

(Can't set to "wontfix", thus using "invalid").

Changed in malone:
assignee: allenap → pitti
status: Confirmed → Invalid
assignee: pitti → nobody
Revision history for this message
Gavin Panella (allenap) wrote :

Setting to Won't Fix as suggested by Martin.

Changed in malone:
status: Invalid → Won't Fix
Revision history for this message
Martin Pitt (pitti) wrote :

FYI, this has been implemented on the client-side in bug 124338 .

Revision history for this message
Shahar Or (mightyiam) wrote :

Dear interested parties,

I've experienced what Scott said. I've been creating dupes to so that the report collected by apport to be uploaded.

Should I not do that?

Many blessings.

Revision history for this message
Martin Pitt (pitti) wrote :

Sharar,

you can still do that, but you can also use the new 'apport-collect' tool to augment an existing bug. Please see https://lists.ubuntu.com/archives/ubuntu-devel-announce/2009-February/000535.html .

Revision history for this message
Martin Pitt (pitti) wrote :

BTW, as Jane noted in bug 352293, the current method generates a plethora of mail for each user who submits additional info to an existing bug, due to Launchpad not merging several attachments in one bug mail. Do you think it's easier to implement the original proposal here, or to merge bug mail for several attachments? (The latter would be even nicer, I think).

Thanks!

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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