Actions
bug #7722
closedNamePopupEditor: validation not working for rank genus
Status:
Closed
Priority:
Highest
Assignee:
Category:
cdm-vaadin
Target version:
Start date:
Due date:
% Done:
100%
Estimated time:
Severity:
normal
Found in Version:
Description
Validation button of genus without function (basionym, replaced syn. okay)
Files
Updated by Andreas Kohlbecker over 5 years ago
- Subject changed from Vaadin UI Validation of genus missing to NamePopupEditor: validation not working for rank genus
- Target version changed from Unassigned CDM tickets to Release 5.2
Updated by Andreas Kohlbecker over 5 years ago
- Status changed from New to Feedback
- Assignee changed from Andreas Kohlbecker to Wolf-Henning Kusber
- Priority changed from New to Highest
- Target version changed from Release 5.2 to Release 5.3
the validation has explicitly limited to ranks at SpeciesOrBelow. Is it sufficient to also include genus an below or do we also need higher ranks?
Updated by Wolf-Henning Kusber over 5 years ago
- Assignee changed from Wolf-Henning Kusber to Andreas Kohlbecker
It could be that people validate higher rank names, too.
Updated by Andreas Kohlbecker over 5 years ago
- Status changed from Feedback to Resolved
- % Done changed from 0 to 50
Applied in changeset cdm-vaadin|e8e0ad3ba36e287dc5fc1c398bc505f3f0a5a38e.
Updated by Andreas Kohlbecker over 5 years ago
- Assignee changed from Andreas Kohlbecker to Wolf-Henning Kusber
solved, please review
Updated by Wolf-Henning Kusber over 5 years ago
- Status changed from Resolved to Closed
- Assignee changed from Wolf-Henning Kusber to Andreas Kohlbecker
- % Done changed from 50 to 100
perfect !
Actions