Task #8815 (closed)
Bug: Creation/Deletion of ROI
Reported by: | jburel | Owned by: | jburel |
---|---|---|---|
Priority: | major | Milestone: | OMERO-4.4 |
Component: | Insight | Version: | n.a. |
Keywords: | n.a. | Cc: | rkferguson, saloynton |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | 0.0d |
Sprint: | 2012-05-22 (15) |
Description (last modified by jburel)
Creation/Deletion of ROIs in read-only group
- user-6 can see ROI on image belonging to user-2 - created by user-2. Correct
- user-6 can create ROI on image belonging to user-2. Correct
- user-2 can see ROI added by user-6. Correct
- when user-2 deletes ROIs, own deleted but ones added by user-6 not deleted. Correct
- user-2 can edit text ROI added by user-6. Bug
- when deleting all ROI user-2 additions were deleted in one instance and retained in other - inconsistent behaviour. Hummm
Usability Issue - forced to delete all ROIs, cannot retain some and delete others. NOTE: Subsequently told can delete individual ROIs with delete key - no way for user to know this. To be moved to another ticket if required. Information in the g.doc
Change History (7)
comment:1 Changed 12 years ago by jburel
comment:2 Changed 12 years ago by rkferguson
Read-only-1
comment:3 Changed 12 years ago by jburel
- Description modified (diff)
- Remaining Time set to 0.2
- Status changed from new to accepted
comment:4 Changed 12 years ago by jburel
- Description modified (diff)
comment:5 Changed 12 years ago by jburel
bigger than anticipated. I need to review the generation of the roi object.
comment:6 Changed 12 years ago by jburel
- Remaining Time changed from 0.2 to 0
- Resolution set to fixed
- Status changed from accepted to closed
comment:7 Changed 12 years ago by jburel <j.burel@…>
(In [339f3b9b1d41f3ee20ad101ebbc2af8b03388768/ome.git] on branch develop) Review permissions and figure manipulation (see #8815)
Add method canAnnotate, canDelete etc
so that group owner and admin can manipulate roi.
Gus: could indicate the group you were looking at since user-2 is in 2 groups.
One bug for sure to fix: edit
maybe a second one if the group is private.