Launchpad itself

Shouldn't be possible to change status/assignee/importance/milestone of a duplicate bug

Bug #54801 reported by Guilherme Salgado
20
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Matthew Paul Thomas

Bug Description

Today I overlooked bug 54716 (which was marked as a dupe of 42064) and ended up confirming it and assigning it to myself. This should either be impossible or there should be a more appealing message to stop me from doing such a stupid thing.

Tags: lp-bugs ui
Matthew Paul Thomas (mpt)
Changed in malone:
importance: Untriaged → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Diogo Matsubara (matsubara) wrote :

Bug 3796 would help fix this.

Christian Reis (kiko)
Changed in malone:
assignee: nobody → kiko
status: Confirmed → In Progress
Christian Reis (kiko)
Changed in malone:
status: In Progress → Fix Committed
Revision history for this message
Christian Reis (kiko) wrote :

This has recently regressed for 1.0; Matthew has said it will be sorted out.

Changed in malone:
assignee: kiko → mpt
status: Fix Committed → Confirmed
Matthew Paul Thomas (mpt)
Changed in malone:
importance: Medium → High
Matthew Paul Thomas (mpt)
Changed in malone:
status: Confirmed → In Progress
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Fixed in RF 4610.

Changed in malone:
status: In Progress → Fix Committed
Revision history for this message
Christian Reis (kiko) wrote :

I want to register my continued dismay at this solution; I find displaying status and importance of a duplicate bug /very/ confusing.

Revision history for this message
Daniel Holbach (dholbach) wrote :

The current solution is somewhat buggy.

Bug 6538 has ubuntu-gnome as an assignee; a team, which we don't use anymore. I can't unassign the bug from the team and I can't unsubscribe the team from the bug.

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

I guess if we did proper dupe handling we'd clear the assignee and bugwatch link when marking as a duplicate. Undoing becomes more painful then, but we could at least store what was done in a comment.

Matthew Paul Thomas (mpt)
Changed in malone:
status: Fix Committed → Fix Released
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

I think that marking a bug report as a duplicate, and then removing the duplicate marking, should be a no-op. Apart from two (or, if done within five minutes, zero) mail notifications, nothing else should change.

Therefore, I don't think the assignee should be removed from duplicates.

Therefore, I think we should instead directly solve whatever Daniel's problem is with having an assignee in a duplicate bug report. Daniel, what annoyance is it causing? Is it showing up in a bug listing where it shouldn't be? Is it preventing you from retiring the team? Is it causing unwanted bugmail?

Revision history for this message
Daniel Holbach (dholbach) wrote :

It's causing unwanted bugmail.

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

That's a good point. I've reported that problem as bug 137408.

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.