www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "#asfinfra IRC Bot (JIRA)" <j...@apache.org>
Subject [jira] Closed: (INFRA-3031) Update user permissions and/or Project Lead for Apache Qpid
Date Thu, 30 Sep 2010 21:55:39 GMT

     [ https://issues.apache.org/jira/browse/INFRA-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

#asfinfra IRC Bot closed INFRA-3031.

    Resolution: Fixed

> Update user permissions and/or Project Lead for Apache Qpid
> -----------------------------------------------------------
>                 Key: INFRA-3031
>                 URL: https://issues.apache.org/jira/browse/INFRA-3031
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: JIRA
>            Reporter: Robbie Gemmell
> Hi,
> I am going to be release managing the next release of Apache Qpid, but in looking over
JIRA jsut now I noticed I am no longer able to access the options to Manage the project (in
order to create new versions etc), which I was previously able to do.  joes4 mentioned on
#asfinfra that this is because we now use Roles for JIRA. Can the Roles be updated for the
Qpid project to allow the qpid-developers user group this permission again?
> On a related note, I also see that our Project Lead is still listed as Cliff Schmidt
in JIRA, something I imagine that we should have requested be changed when we graduated (ages
ago). Can this please be updated to be our project Chair, Carl Trieloff (cctrieloff)? Presumably
he would then have the administration rights necessary to assign out the desired permissions
to the rest of us if you arent able/dont want to do that directly. Alternatively, I see that
some projects have 'ZZZZ Developers' listed as their lead....does that require creating a
new user account with shared details, or is that just assigned to the JIRA group (ie qpid-developers)?

> Thanks,
> Robbie

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message