You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2015/10/28 05:16:27 UTC

[jira] [Commented] (INFRA-10652) Create new JIRA permission scheme for the YETUS project and add Release Note field.

    [ https://issues.apache.org/jira/browse/INFRA-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977687#comment-14977687 ] 

Sean Busbey commented on INFRA-10652:
-------------------------------------

I believe Chris was just talking about *additional* privileges we are looking for; we're fine with contributors being assignable (as they currently are).

I think we're fine with them having the ability to resolve/close if it's easier to change our permissions by allowing that. Is there any place I can see the full set of permissions done in Default+Contributors?

> Create new JIRA permission scheme for the YETUS project and add Release Note field.
> -----------------------------------------------------------------------------------
>
>                 Key: INFRA-10652
>                 URL: https://issues.apache.org/jira/browse/INFRA-10652
>             Project: Infrastructure
>          Issue Type: Task
>          Components: JIRA
>            Reporter: Chris Nauroth
>            Assignee: Gavin
>
> The Yetus project would like to request a new project-specific JIRA permission scheme.  Please start by cloning the Default Permission Scheme, which is the scheme currently in effect for the YETUS project.  Then, apply the following changes.
> 1. Give the "Contributors" role the "Transition Issues" permission.
> 2. Give the "Contributors" role the "Assign Issues" permission.
> Additionally, we'd like to request the addition of the Release Note field, already commonly used in other projects like HADOOP.



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