Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,406
Community Members
 
Community Events
176
Community Groups

After upgrading FishEye to 4.1 read permissions are missing in the repositories

After upgrading FishEye to 4.1 all read permissions are missing in the repositories:

image2016-7-5 14:45:41.png

The only way I found so far is to add all groups again with "Read" access. Is there any way to fix this without going through all 120 repositories and readding every 3+ groups per repository one by one?

1 answer

1 vote
Kamil Cichy Atlassian Team Jul 05, 2016

Hi @Gerald Schneider,

We are aware of this problem and we're fixing it with priority "Critical".
 https://jira.atlassian.com/browse/FE-6598

We will soon (in a couple of days) release FishEye 4.1.1 which will fix this issue.

If you cannot wait that long and you need an immediate fix, you need to manually modify a DB table. Please let me know if you'd like some guidance on how to do that.

Kamil

Thanks, I just discovered the linked Issue myself. A temporary solution I can think of would be to add an additional column to the table and store the correct group name there, so I can retrieve it again after the issue is solved.

Would a modification like this survive the next update, or would the table in the database be reset to the "correct" structure?

Kamil Cichy Atlassian Team Jul 05, 2016

Please see my answer at the linked issue.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events