Assignee can't unassign himself from specification

[Sebastien Bacher]

The specification https://blueprints.launchpad.net/ubuntu/+spec/integrity has been assigned to me by somebody who I don't know and launchpad doesn't let me unset it because I don't have the permissions. Something is wrong there, random people should not be able to assign somebody to a specification without getting the approval of whoever is concerned and the assignee should be able to change the setting

See also bug 177508, about disclosing who subscribed you to a blueprint.

[William Grant (wgrant)]

Someone decided that ~dct was the approver of one of the blueprints on the debimag project. Everyone is getting spammed, but there's no way to stop it (other than going to ~admins).

[Diogo Matsubara (matsubara)]

The permission to set the assignee seems correct. Someone with a role in the specification, the spec target or the spec goal is allowed to set the assignee.
We can't see who did it because of bug 177508.
The real bug is the fact that even having a role in the spec, as the assignee, seb can't unassign himself.

[Diogo Matsubara (matsubara)]

I just noticed that, while reproducing this bug locally, I got the following notification:

From: Sample Person <email address hidden>
Date: Tue, 06 May 2008 19:22:30 -0000
To: <email address hidden>
Subject: [Blueprint media-integrity-check] CD Media Integrity Check
Reply-To: Sample Person <email address hidden>
X-Spambayes-Classification: ham; 0.00

Blueprint changed by Sample Person:

    Assignee: (none) => No Privileges Person

--
  CD Media Integrity Check
  http://blueprints.launchpad.dev/ubuntu/+spec/media-integrity-check

So I think bug 177508 is fixed. :-)