After upgrading FishEye to 4.1 all read permissions are missing in the repositories:
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".
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.
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?
Welcome to your weekly Jira Ops Early access program update, where we’re sharing news and updates on Jira Ops' progress as we work toward our 1.0 release. If you ever want to drop us feedback or idea...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs