Bug #3136

Validation of level of description should take into account levels custom added by users

Added by Jesús García Crespo over 12 years ago. Updated over 6 years ago.

Status:NewStart date:
Priority:LowDue date:
Assignee:-% Done:


Target version:-
Google Code Legacy ID:atom-1186 Tested version:
Sponsored: Requires documentation:


Now, the validation of level of description values is very simple. We should add checks for level
values custom added by users and take into account the custom order, established by the user in
the term treeview by drag'n'drop. This probably makes necessary some modifications on Qubit ORM
to make available methods like moveToNextSiblingOf(...).

Peter described all the details here,

[g] Legacy categories: Form validation


#1 Updated by Peter Van Garderen over 12 years ago

see related /p/qubit-toolkit/issues/detail?id=1289

#2 Updated by Anonymous about 12 years ago

  • Priority changed from Critical to High

[g] Labels added: Priority-High
[g] Labels removed: Priority-Critical

#3 Updated by David Juhasz almost 12 years ago

  • Priority changed from High to Medium

[g] Labels added: Priority-Medium
[g] Labels removed: Priority-High

#4 Updated by Anonymous almost 12 years ago

  • Priority set to Low

[g] Labels added: Priority-Low

#5 Updated by Evelyn McLellan over 11 years ago

  • Target version set to Release 1.2

Moved to 1.2.

[g] Labels added: Milestone-Release-1.2

#6 Updated by David Juhasz over 10 years ago

  • Target version set to Release 1.3

Roll over to Release 1.3

[g] Labels added: Milestone-Release-1.3

#7 Updated by Jesús García Crespo over 6 years ago

  • Assignee deleted (Jesús García Crespo)

Also available in: Atom PDF