Changes between Initial Version and Version 1 of Ticket #1360


Ignore:
Timestamp:
Aug 24, 2009, 8:18:53 AM (15 years ago)
Author:
Nicklas Nordborg
Comment:

This is not the desired behaviour. I think it is something that happens if changes are made to the protocol and/or the annotation type in such a way that the annotation type no longer can be used on new items of the same type. The procedure described above is just one way of many to achive this.

I think that already existing annotations should be visible when editing annotations.

A workaround is to use the "Overview" tab. This will list the existing annotations and will probably also give a warning about the annotation not being a protocol parameter of the used protocol. Use the links on the "Overview" page to edit/remove the annotation. There are several links, but one of them give the same error as in #1361 (Unhandled item: ANNOTATION....).

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1360

    • Property MilestoneBASE 2.13
    • Property Owner changed from everyone to Nicklas Nordborg
    • Property Status newassigned
  • Ticket #1360 – Description

    initial v1  
    11How to reproduce:
    2 1) create annotation type AT being protocol parameter and allow it for items of type IT
    3 2) add protocol parameter PP of type AT to protocol P
    4 3) create an ITEM of IT type, select protocol P and annotate with protocol parameter PP
    5 4) remove PP from parameters of protocol PP
     2 1. create annotation type AT being protocol parameter and allow it for items of type IT
     3 2. add protocol parameter PP of type AT to protocol P
     4 3. create an ITEM of IT type, select protocol P and annotate with protocol parameter PP
     5 4. remove PP from parameters of protocol PP
    66
    77The ITEM will still have the annotation of type AT, but it will not be shown in list of ITEM's annotations, so it can't be deleted/altered. Is this desired behavior? Maybe one should not be able to remove protocol parameter if there are items using it?