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?
This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...
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