Task #11538 (closed)
Opened 11 years ago
Closed 11 years ago
BUG: Move from read-write
Reported by: | pwalczysko | Owned by: | web-team@… |
---|---|---|---|
Priority: | major | Milestone: | 5.0.0-rc1 |
Component: | Web | Version: | 5.0.0-beta1 |
Keywords: | n.a. | Cc: | ux@…,, jamoore |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description (last modified by pwalczysko)
When testing the read-write workflow,functionality Move, read-write being the group of origin.
Error in Web (Howe): Non-owner owner 13
Error in Gretzky : Non-owner owner 7
See screenshot
Workflow:
- open Insight
- login as user-6 (admin) on Howe
- Import As user-10, group read-write
- Link the data into a Project of user-5
- Do not create a new folder on import - import couple of dv images
- Import is successful, data are owned by user-10, located in a Project of user-5
- login to Web as user-5
- try to move the Project to read-annotate group
- the move fails, with a message : non-owner owner 13
- the data are gone from the original group
- the data are not in the target group
Attachments (2)
Change History (11)
Changed 11 years ago by pwalczysko
comment:1 Changed 11 years ago by pwalczysko
Changed 11 years ago by pwalczysko
comment:2 Changed 11 years ago by pwalczysko
The; linking problem described above for develop is reported in https://trac.openmicroscopy.org.uk/ome/ticket/11546.
comment:3 Changed 11 years ago by pwalczysko
- Description modified (diff)
comment:4 Changed 11 years ago by pwalczysko
- Milestone changed from OMERO-4.4.10 to 5.0.0-beta2
- Version changed from 4.4.8 to 5.0.0-beta1
comment:5 Changed 11 years ago by pwalczysko
Moving to 5.0.0-beta2 as this is also a develop problem and it is a full-loss-of-data bug. Discovered during the testing to switch the read-write group on.
comment:6 Changed 11 years ago by pwalczysko
Just was able to confirm the bug on Gretzky. Because the choice of the Project was fixed, you can link the image imported as user-10 to user-5's Project at Import stage now.
comment:7 Changed 11 years ago by pwalczysko
This move proceeds as expected in Insight.
comment:8 Changed 11 years ago by wmoore
- Priority changed from critical to major
When I try to reproduce this, the move fails in web and Insight. The data is removed from the Tree during move, and is not shown again when move fails. However, when the Tree is refreshed, the data reappear. The behaviour is identical in both clients. The only option is to add a "Refresh" button to the "Move failed" message in activities panel (we don't want to auto-refresh since you might lose your place if that happens when you're working on something else.
comment:9 Changed 11 years ago by wmoore
- Resolution set to duplicate
- Status changed from new to closed
Assuming the main issue here is how to refresh the tree after a failed chgrp, then it's a duplicate of #11129. Closing.
The same situation is on Gretzky, on develop. The only difference is that the warning trianlge is red on Gretzky, whereas on dev_4_4 you get a green tick (see screenshots). The workflow is identical with Howe, except that on Gretzky, you have to link the dataset with the images to the Project post-import. The linking during import does not work on develop, because the Import Location window does not show the P/Ds belonging to other users (this will be filed in a separate ticket).