infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Marru (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (INFRA-18757) Fork JIRA Permission Scheme
Date Tue, 16 Jul 2019 17:03:00 GMT

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

Suresh Marru resolved INFRA-18757.
----------------------------------
    Resolution: Fixed

Thanks Gavin, It is working as we desire, we are all set. 

> Fork JIRA Permission Scheme
> ---------------------------
>
>                 Key: INFRA-18757
>                 URL: https://issues.apache.org/jira/browse/INFRA-18757
>             Project: Infrastructure
>          Issue Type: Task
>          Components: JIRA
>            Reporter: Suresh Marru
>            Assignee: Gavin
>            Priority: Major
>
> For Apache Airavata, we would like to to have users and contributors assign JIRA's and
resolve them. Can we please request the default scheme be forked for Airavata and make users
and contributors to be added to 'Assignable User' and 'Assign Issues' in the permissions?
> Also, we see a redundant "Contributors 1" role, can we please request that to be removed
and also remove the "Developer" role? 
> Thanks,
> Suresh



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Mime
View raw message