Re: [hibernate-dev] Relaxing JIRA assignment restrictions
If you want to take over management of groups and other security concerns
in Jira from me, I am all for that ;)
Look for the global groups developers and dev-team and their usage. I
think its things like the ability to close issues, re-open them, etc.
Sorry, I am swamped and dont have time to fully research. I looked quickly
but Jira's permissions are not easy to sift through imo
On Tue, Nov 21, 2017 at 9:39 AM Sanne Grinovero <sanne(a)hibernate.org> wrote:
On 21 November 2017 at 15:33, Steve Ebersole
<steve(a)hibernate.org> wrote:
> Because we allow certain elevated privileges to people who can be
assigned
> issues.
Do you have a concrete example? I'm happy to reconfigure "certain
elevated privileges" to work on the proper group rather than depending
on assign-ability, if you could hint me into what kind of things I
should look out for.
I'd just want the option to assign issues to anyone in the "users" group.
This is apparently now an option in JIRA, and would allow people in
"users" to self-assign issues - as long as they are the issue creator.
Seems useful?
Thanks,
Sanne
>
>
> On Tue, Nov 21, 2017, 6:57 AM Sanne Grinovero <sanne(a)hibernate.org>
wrote:
>>
>> Hi all,
>>
>> I'm being frequently asked to add new contributors to "the right
>> groups" on JIRA just for the sake of being able to assign issues to
>> them.
>>
>> I'm not sure why it's useful to prevent this for anyone to do being
>> able to do this, and also I suspect some people might be more inclined
>> to "just do it" if they had a clearer, more welcoming approach to
>> signal that they're looking into the issue themselves.
>>
>> Any objections to relax this requirement?
>>
>> Thanks,
>> Sanne
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev