Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #12544 (closed)

Opened 10 years ago

Closed 9 years ago

Bug: Inter-group links may be created

Reported by: mtbcarroll Owned by: mtbcarroll
Priority: critical Milestone: 5.1.0-m3
Component: General Version: 5.0.3
Keywords: n.a. Cc: ux@…, bpindelski, bramalingam, cblackburn
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

  1. start with a fresh database
  2. run create_users script from omero-setup
  3. start up Insight
  4. log in as root
  5. create read-annotate group read-annotate with owner read-annotate-owner
  6. create private group private with owner private-owner
  7. create new user 'image-owner' who is a member of both read-annotate and private
  8. create new user 'tag-owner' who is a member of both read-annotate and private
  9. switch user to image-owner
  10. import two images into read-annotate
  11. switch user to tag-owner
  12. tag both image-owner's images with the same new tag
  13. switch user to image-owner
  14. (shell) as root run bin/omero hql --all 'select parent.details.group.id, child.details.group.id from ImageAnnotationLink' and observe that for each row the group ID in Col1 matches that in Col2
  15. right-click one of the images and move it to private
  16. (shell) as root run bin/omero hql --all 'select parent.details.group.id, child.details.group.id from ImageAnnotationLink' and recoil in horror

Note that our usual test user setup does not include a regular user who is in both a read-annotate and a private group.

https://github.com/openmicroscopy/openmicroscopy/pull/2401 has SQL for deleting existing inter-group annotations, though note that the set of annotatable classes has since changed.

#11779 should fix this bug, but it definitely seemed worth documenting.

Change History (6)

comment:1 Changed 10 years ago by jamoore

  • Cc bpindelski bramalingam cblackburn added
  • Milestone changed from 5.1.0 to 5.1.0-m3
  • Priority changed from major to critical

Makes sense. Perhaps the most critical thing to come from this will be a test then?

comment:2 Changed 9 years ago by jamoore

  • Owner changed from jamoore to mtbcarroll

Passing to mark along with 11752

comment:3 Changed 9 years ago by jburel

Keeping it m3 since the work is on-going and will probably be completed during that milestone.

comment:5 Changed 9 years ago by mtbcarroll

  • Status changed from new to accepted

comment:6 Changed 9 years ago by mtbcarroll

  • Resolution set to fixed
  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.103255 sec.)

We're Hiring!