On 28 Jul 2016, at 14:34, Max Rydahl Andersen
On 28 Jul 2016, at 14:16, Marcel Bruch wrote:
> I just checked your roles. You only got Reporter rights assigned (the default) b/c
your teams devdoc and website were not enabled for reviewer access by your org-admins.
what does reviewer access mean in this context ?
There are three roles: reporters, reviewers and org-admins. Reporters can only see public
information of a problem while reviewers can edit data, create bugs etc. org-admins can
administrate different aspects of the installation.
Would it be sufficient to add a read-only group that have access to
all repos and add everyone without push access to look ?
I’ve discussed several options with Fred and Alexey last week.
Just repeating them briefly:
1. If all organization members should get reviewer access, simply do no select any team.
We’ll then check membership against the organization members.
2. It may make sense to create a group especially for accessing error reports (e.g. aeri).
There simply add everyone who needs access to error reports.
3. If some teams should not / do not require access to error reports, simply do not select
their teams in the oauth authorization panel - that’s what’s used ATM.
Whatever you decide, just update the configuration - or let me know.
Please note that you still can log in with the previously used username/password.
> Org-admins, is this an oversight?
>> BTW, https://redhat.ctrlflow.com/
> Agreed, we should make this more meaningful again.
> jbosstools-dev mailing list
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940