Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Best user management practices for Fisheye?

Hi everyone,

We have added all users to a new directory in Crowd that syncs up with Fisheye, but I was wondering if there were any best practices you've found along the way for user management in the web interface.

Would it be to set up separate groups in Crowd for each repository/project, or set up groups in Fisheye itself for each? Or maybe just add individual users to the group?

Looking to see what others have done to make things easier. We currently only have a 50 person license, so it would be ideal to find out now before expanding.

We are currently running version 4.8.0.

Thanks all!

1 answer

I would use the "keep it simple" model. If it's OK for everyone to have access to everything, why restrict? If you have 3rd party QA and you only want them to see certain things, you could create "employees" and "external" groups, populate them with the appropriate users and use those two groups to manage access.  I wouldn't recommend using granular repo permissions unless you need to, though. It just seems to cause more problems than it's worth when we see clients doing this.

Assuming you are connecting Fisheye to Jira, there is a permission called "View development tools" that controls which users have the repo details show up on the associated Issue. This is useful if you want your developers to see that information, but not your business users, for example.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
Community showcase
Published in Confluence

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

109 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you