Limiting fisheye users copied from Jira

Tim Collier
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 20, 2013

I am using JIRA for authentication (and it is using corporate ldap). But, a number of my jira users - testers and buisiness, dont need access to fisheye. I would like to be able to allow the ~50 developers from jira to access fisheye but not the rest (~100).

What is the easiest way to accomplish this?

should I use groups?

should i manually manage the fisheye users?

Right now jira-developers, jira-users, and jira-admin groups have been created in fisheye from jira.

What would you suggest?

1 answer

1 accepted

1 vote
Answer accepted
Grzegorz Dlugoszewski
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 20, 2013

Hi.

Yes, you should use groups. If your "jira-developers" group contains only developers who shold be able to access fisheye then you're good to go. When you set up Fisheye to use external (jira) userbase you can choose which groups should be allowed to access. Simply choose only "jira-developers" (and probably "jira-admin" just in case) and those will be the only users who will be allowed to login to Fisheye.

It's all described here: https://confluence.atlassian.com/display/FISHEYE/Loading+Users+from+Active+Directory%2C+LDAP%2C+Crowd+or+JIRA

If you expect that the number of Fisheye users will grow in the future and expand beyond only developers, you could create "fisheye-users" group in JIRA. This group should contain your developers but will also give you space to add some non-development users to fisheye and not mess your jira-only settings related to "jira-developers" group.

Hope this helps you.

Cheers!

Tim Collier
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 25, 2013

Thanks - I appreciate the prompt reply

Suggest an answer

Log in or Sign up to answer