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 #9064 (closed)

Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

Bug: Allow admin to move between groups they are not a member of

Reported by: saloynton Owned by: wmoore
Priority: blocker Milestone: OMERO-4.4
Component: Web Version: n.a.
Keywords: n.a. Cc: web-team@…
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: 2012-06-19 (17)

Description

The web is still missing the critical functionality for
an admin in the web of moving between groups they are not a member of.

Attachments (2)

Screen shot 2012-06-06 at 17.58.21.png (63.7 KB) - added by saloynton 12 years ago.
Screen shot 2012-06-06 at 17.58.33.png (31.3 KB) - added by saloynton 12 years ago.

Download all attachments as: .zip

Change History (9)

comment:1 Changed 12 years ago by saloynton

  • Cc web-team@… added
  • Sprint set to 2012-06-19 (17)

comment:2 Changed 12 years ago by wmoore

  • Resolution set to fixed
  • Status changed from new to closed

comment:3 Changed 12 years ago by saloynton

Will I was having a run through this and noticed the blue line in the drop down menu, I am logged in a user 6 looking from the read-write-1 group. The blue line appears on read-only, read-annotate and private in the drop down list. See the screenshots attached.

Changed 12 years ago by saloynton

Changed 12 years ago by saloynton

comment:4 Changed 12 years ago by saloynton

  • Resolution fixed deleted
  • Status changed from closed to reopened

I have re-opened this to check if the issue identified were related to any changes in this ticket?

Last edited 12 years ago by saloynton (previous) (diff)

comment:5 Changed 12 years ago by wmoore

  • Resolution set to invalid
  • Status changed from reopened to closed

This has nothing to do with this ticket or the changes above. It's simply that the user ID 52 in the database does not have a first-name or last-name. Since the username is "Melissa" I think this account was created via LDAP. LDAP must not be configured to set First name and Last name.

comment:6 Changed 12 years ago by jburel

I agree that it is a different issue but such case should be supported since the first name and last name are not required. A new ticket has to be created.

comment:7 Changed 12 years ago by wmoore

See #9110 for handling first-name last-name display.

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.68011 sec.)

We're Hiring!