Permission to change project roles is restricted to admins / PMC,
naturally. I don't know if it's documented beyond this that Gavin
helpfully pasted:
https://cwiki.apache.org/confluence/display/SPARK/Jira+Permissions+Scheme
Another option is to make the list of people who you can assign to
include
On Thu, Apr 23, 2015 at 5:26 PM, Sean Owen wrote:
> Following my comment earlier that "I think we set Assignee for Fixed
> JIRAs consistently", I found there are actually 880 counter examples.
> Lots of them are old, and I'll try to fix as many that are recent (for
> the 1.4.0 release credits) as
On Thu, Apr 23, 2015 at 5:47 PM, Hari Shreedharan wrote:
> You’d need to add them as a contributor in the JIRA admin page. Once you
> do that, you should be able to assign the jira to that person
>
>
>
Is this documented, and does every PMC (or committer) have access to do
that ?
>
>
> Thanks,
You’d need to add them as a contributor in the JIRA admin page. Once you do
that, you should be able to assign the jira to that person
Thanks, Hari
On Thu, Apr 23, 2015 at 5:33 PM, Shivaram Venkataraman
wrote:
> A related question that has affected me in the past: If we get a PR from a
> ne
A related question that has affected me in the past: If we get a PR from a
new developer I sometimes find that I am not able to assign an issue to
them after merging the PR. Is there a process we need follow to get new
contributors on to a particular group in JIRA ? Or does it somehow happen
automa
Following my comment earlier that "I think we set Assignee for Fixed
JIRAs consistently", I found there are actually 880 counter examples.
Lots of them are old, and I'll try to fix as many that are recent (for
the 1.4.0 release credits) as I can stand to click through.
Let's set Assignee after res
