You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2014/09/29 21:09:35 UTC

[jira] [Assigned] (INFRA-8402) Allow JIRAs to be assigned to people in the developers group in Spark

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

Gavin reassigned INFRA-8402:
----------------------------

    Assignee: Gavin

> Allow JIRAs to be assigned to people in the developers group in Spark
> ---------------------------------------------------------------------
>
>                 Key: INFRA-8402
>                 URL: https://issues.apache.org/jira/browse/INFRA-8402
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: JIRA
>            Reporter: Xiangrui Meng
>            Assignee: Gavin
>
> Spark project has several groups (https://issues.apache.org/jira/plugins/servlet/project-config/SPARK/roles):
> 1. committers
> 2. contributors
> 3. developers
> We added many people to the contributors group in order to assign JIRAs to them. However, this group can also do the following:
> 1. Modify "fixed versions" and other fields.
> 2. Assign a JIRA to themselves by clicking "Start Progress".
> We want to have a group, e.g., developers, who in the group can be assigned to JIRAs. But they cannot modify fields like "fixed versions" and find a way to get JIRA assigned to themselves. This is important for project management and it helps reduce duplicate efforts.
> Basically, we want the "assignee" field to accept people from the "developers" group and then we can move some contributors to developers. This provides an alternative solution to INFRA-8365.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)