being driver of project/project-group does not give me "Triage" powers

[Alexander Sack]

 + i am member of linaro-drivers
 + linaro-drivers is the driver for linaro-cloud-buildd project group
 + linaro-cloud-buildd project group has a project linaro-android-build-tools
 + linaro-drivers shows correctly up as the driver of linaro-android-build-tools
 + https://help.launchpad.net/HelpText/ProjectOverview/Driver suggest that this should give me powers to change bug status to triaged

Bug: I cannot change lp:744648 to Triaged even though its a bug filed against linaro-android-build-tools.

[Deryck Hodge (deryck)]

It's maintainers and bug supervisors that have this power, not drivers. The docs are wrong and should be fixed. Drivers should probably be added to the canTransitionToStatus check, which would be an easy fix.

[Alexander Sack (asac)]

please explain to me what powers drivers gain then. For us in linaro drivers are completely useless then. Also bug supervisors automatically get all the mail.

[Alexander Sack (asac)]

anyway, would love to see the "specificatioN" of what each role in a project can do ... I see:

 + maintainer
 + driver
 + release manager (kind of driver for a series, but doesnt give triaging/importance powers either it seems)
 + bug supervisor

if you say above that drivers should really get that power, please consider raising importance a bit. For us it would be really great to have driver role with useful powers. thats for a) bugs and b) blueprints (here i think drivers don't have much more power either).

[Alexander Sack (asac)]

subscribed salgado: do you know whats going on here? feels really broken this driver feature.

[Guilherme Salgado (salgado)]

It looks like only bug supervisors (or the project owner) can do that.

    def canTransitionToStatus(new_status, user):
        """Return True if the user is allowed to change the status to
        `new_status`.

        :new_status: new status from `BugTaskStatus`
        :user: the user requesting the change

        Some status transitions, e.g. Triaged, require that the user
        be a bug supervisor or the owner of the project.
        """

I'm not sure whether it's the docs that need to be fixed or the code,
though.

[Alexander Sack (asac)]

guys, this makes no sense. Project drivers have absolutely zero additional powers atm.

What they need to be able to do is:

 1. create new milestones
 2. create new series
 3. change bug status tasks
 4. approve blueprnts for series etc.

If you disagree, please give me accurate info what powers drivers have (on top of normal member). Then we can talk about that list.

[William Grant (wgrant)]

Series and project drivers can edit milestones. Series drivers can create milestones (project drivers probably should be able to too). Project drivers can create series. Project drivers can edit and administer blueprints, including their series targets. Project drivers can target bugs to series.

Your statement that they have no additional powers is clearly absolutely false, and they probably have other powers that I cannot immediately recall. The driver is a release management role; their powers largely pertain to release management. Bug statuses are controlled by a separate role, the bug supervisor.