infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Freddy Barboza (JIRA)" <>
Subject [jira] [Updated] (INFRA-9513) Implement additional changes to Spark JIRA permission scheme
Date Wed, 01 Feb 2017 02:37:51 GMT


Freddy Barboza updated INFRA-9513:
    Status: Waiting for Infra  (was: Waiting for user)

> Implement additional changes to Spark JIRA permission scheme
> ------------------------------------------------------------
>                 Key: INFRA-9513
>                 URL:
>             Project: Infrastructure
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: JIRA
>            Reporter: Sean Owen
>            Assignee: Freddy Barboza
>            Priority: Minor
> Following on I think Spark is ready
to request some additional changes to the JIRA permission scheme in effect for the project.
> I am not sure how much of this is possible, but here's the wish list:
> - Make Component and Affects Version required for new JIRAs 
> - Set default priority to Minor and type to Question for new JIRAs. 
> - Only let Committers set Target Version and Fix Version 
> - Only let Committers set Blocker Priority 
> - Restrict or remove certain issue types (e.g. Temp or Test)
> - Provide a default Description that links to the contribution guide
> I can do as much of the legwork here as is possible for us to do, I just wasn't sure
how or where to make the changes.
> Thanks!

This message was sent by Atlassian JIRA

View raw message