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
In case we want to copy/move an object (a data object or collection) from our home collection to the any group which we are member of, we cannot do this through Metalnx. This issue exist also among the groups (cant copy/move from one group to another). Because the "groups" tab on the popped-up does not bring the collection structure of the groups that we have access to. On "Collections" tab I can only see my home collection in addition to the public collection. After clicking on the "Groups" tab, nothing changes.
Copy screen:
Move screen:
The only workaround seems that;
Before copying/moving, first add the collection of the group that you want to in your favorites,
Then choose your target collection in "Favorites" tab on the popped-up page.
But this is not a user friendly solution.
Note : Tested both in 4.2.8 - 2.4.0 and in 4.2.9 - 2.4.0
The text was updated successfully, but these errors were encountered:
mstfdkmn
changed the title
Can't copy/move data objects and/or collections among groups, and between groups and home
Can't copy/move data objects and/or collections among groups, and between home and groups' collections
Jul 9, 2021
In case we want to copy/move an object (a data object or collection) from our home collection to the any group which we are member of, we cannot do this through Metalnx. This issue exist also among the groups (cant copy/move from one group to another). Because the "groups" tab on the popped-up does not bring the collection structure of the groups that we have access to. On "Collections" tab I can only see my home collection in addition to the public collection. After clicking on the "Groups" tab, nothing changes.
Copy screen:
Move screen:
The only workaround seems that;
But this is not a user friendly solution.
Note : Tested both in 4.2.8 - 2.4.0 and in 4.2.9 - 2.4.0
The text was updated successfully, but these errors were encountered: