• Views
  • Iteration Report
  • My Iteration Report
  •  
OMERO.clients
  • Login
  • Help/Guide
  • About Trac
  • Preferences
  • Wiki
  • Timeline
  • Roadmap
  • Browse Source
  • View Tickets
  • Search

Context Navigation

  • ← Previous Ticket
  • Next Ticket →

Ticket #560 (closed defect: fixed)

Opened 7 months ago

Last modified 7 months ago

Fully lock "template-locked" fields

Reported by: will Owned by: will
Priority: minor Milestone: 3.0-Beta3
Component: protocol Version:
Keywords: Cc:

Description

If field (or it's parent) has had template locked, users should still be able to fully lock this field. This is easy enough for the children of the template-locked field: Simply enable full locking. But, for the template-locked field itself, do you replace the template lock with a full lock (and lose the time-stamp and user who locked the template originally)?

Change History

Changed 7 months ago by will

  • status changed from new to closed
  • resolution set to fixed

Locking (and unlocking) of fields is allowed if an ancestor is template-locked, but not if an ancestor is fully-locked. r5396.

This feature is not fully finished (eg if a field is template-locked, you can only fully lock it by unlocking, then fully locking. This may not be "allowed" if locked by someone else, and it loses the "locking history".

Note: See TracTickets for help on using tickets.

Download in other formats:

  • Comma-delimited Text
  • Tab-delimited Text
  • RSS Feed

Trac Powered

Powered by Trac 0.11
By Edgewall Software.

Visit the Trac open source project at
http://trac.edgewall.org/