You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We first deploy self host image version 2023.5.0. We add a Collection to our Organization. Afeter that, we can add user to Collection and set permission. After upgrade to latest version, we are unable to add user to Collection and set permission (we try with user with different permission, no one is working, even if it is an Administrator).
So, we tried to downgrade to 2023.7.0-beta (that is the oldest version currently available on docker hub) and the problem is still there.
Actually we can't downgrade to 2023.5.0 version, because it is no longer present on docker hub.
We try to search into application log, but there is nothing releated to this problem. The changelogs on github between different versions are useless, as they are very generic. Have there been any changes in the application management functions that may have broken the functionality?
The text was updated successfully, but these errors were encountered:
Thank you for your report, it seems like it is a duplicate of this one #186
If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these.
I have the same problem as issue #186.
We first deploy self host image version 2023.5.0. We add a Collection to our Organization. Afeter that, we can add user to Collection and set permission. After upgrade to latest version, we are unable to add user to Collection and set permission (we try with user with different permission, no one is working, even if it is an Administrator).
So, we tried to downgrade to 2023.7.0-beta (that is the oldest version currently available on docker hub) and the problem is still there.
Actually we can't downgrade to 2023.5.0 version, because it is no longer present on docker hub.
We try to search into application log, but there is nothing releated to this problem. The changelogs on github between different versions are useless, as they are very generic. Have there been any changes in the application management functions that may have broken the functionality?
The text was updated successfully, but these errors were encountered: