Launchpad itself

Should be possible to edit a bug and subscribe to it in one step

Bug #516 reported by Sebastien Bacher
24
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Brad Bollenbach

Bug Description

People doing bug triage want to track the changes and put themself on the Cc field

People doing bug triage often want to track the changes by subscribing themselves to a bug report. Currently this requires going to a separate page, which is not optimal; what took one page load in Bugzilla takes four page loads in Malone.

We should implement the same solution to bug 977 in the editstatus form too.

See original description
Tags: lp-bugs
Revision history for this message
Brad Bollenbach (bradb) wrote :

Checkpoint: seb128, are you happy enough with the changes that have been made to the subscription mechanism sort-of-recently(ish), or do you have a suggestion for how it should be made simpler before we close this report?

Brad Bollenbach (bradb)
Changed in malone:
status: New → NeedInfo
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

The bug hasn't been fixed in any way, so why should the bug report be closed?

description: updated
description: updated
Changed in malone:
status: NeedInfo → New
Revision history for this message
Brad Bollenbach (bradb) wrote :

The pain has been slightly reduced by the fact that you don't actually have to fill in a text field on that separate page anymore (which itself took a few clicks to do.)

But yes, I agree that this is still horrendous and hostile.

Related to this, I documented the most simplistic bug triage workflow possible, with some rather painful results:

    https://wiki.launchpad.canonical.com/MaloneTriageWorkflowSimplification

Changed in malone:
assignee: nobody → bradb
status: New → Accepted
Revision history for this message
Dean Sas (dsas) wrote :

Would there be any time when someone wanted to comment/alter a bug and not be notified if something changes?

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Yes -- comments of the form "This bug is nothing to do with X, reassigning".

Revision history for this message
Dean Sas (dsas) wrote :

Which I'd guess are in the minority, would it be fair for those people to be expected to unsubscribe theirselves? Or to not subscribe them if they reassign the task to something else.

Though maybe that'll surprise the user too much.

Revision history for this message
Christian Reis (kiko) wrote :

It's now a dupe of bug 977, given we can now in-place edit the bug status information.

Revision history for this message
Diogo Matsubara (matsubara) wrote :

I unduped this bug because it's slightly different than bug 977

Diogo Matsubara (matsubara)
description: updated
Brad Bollenbach (bradb)
Changed in malone:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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