You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.