Launchpad bug workflow change

Emmet Hikory emmet.hikory at
Tue Jun 19 23:53:57 UTC 2007

On 6/20/07, Jordan Mantha <mantha at> wrote:
> On Wed Jun 20, 2007 at 01:13:41AM +0200, Henrik Nilsen Omma wrote:
> > If we want a certain group of people who write code but are not MOTU or
> > core-dev to be able to set the whole range of status settings then we
> > can set up a team that gives that access. I agree that people can write
> > valuable code without doing .deb packaging for example.
> OK, but it wasn't so much the new status fields that has people concerned
> as changing who can set the status like:
> "A developer can:
>   * Move the bug from Triaged to ToDo or push it back to a previous category. "
> Why should only a person in ubuntu-dev be able to use ToDo? Other people
> need to be able to set ToDo, In Progress, Fix Commited, and Fix Released.
> ... what is being changed is who can do what. And you previously stated
> that people shouldn't assign themselves to bugs they aren't going to fix. I
> think that is very true and perhaps a solution to the current problem is to
> allow the person who is assigned to a bug to change the status as
> neccessary because that is the person doing the actual work.

    I'd like to endorse this suggestion as a solution to the issue.
The general community member who is not working to fix the bug is very
unlikely to assign themselves to adjust status, whereas those who are
working with the bugs will need to set the status appropriately.
Another workflow example that requires this is a member of bugsquad
who discovers that a bug in a package pulled directly from Debian has
been fixed in a newer version, and needs to set the status to "Fix
Released" with a comment indicating the version in which it is fixed.


More information about the Ubuntu-devel-discuss mailing list