Project

General

Profile

bug #9817

AggregationWizard: Changing the maxRank results in empty minRank

Added by Katja Luther about 1 month ago. Updated about 1 month ago.

Status:
Closed
Priority:
New
Assignee:
Category:
taxeditor
Target version:
Start date:
10/18/2021
Due date:
% Done:

100%

Severity:
blocker
Found in Version:

Description

mail AM:

wenn ich den max-Rank beim DDS Aggregationsdialog ändere wird immer der min-Rang auch gelöscht. Auch in Fällen, wo dies nicht notwendig ist.

Associated revisions

Revision 9f84c595 (diff)
Added by Katja Luther about 1 month ago

fix #9817: remember selected rank when update rank combo

History

#1 Updated by Andreas Müller about 1 month ago

  • Tags set to aggregation, additivity, fast
  • Target version changed from Unassigned CDM tickets to Release 5.29

This is a regression therefore setting to 5.28

#2 Updated by Katja Luther about 1 month ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 50

#3 Updated by Katja Luther about 1 month ago

  • Assignee deleted (Katja Luther)
  • Target version deleted (Release 5.29)
  • Severity changed from normal to blocker

This should be fixed, please review.

#4 Updated by Katja Luther about 1 month ago

  • Assignee set to Andreas Müller
  • Target version set to Release 5.29

#5 Updated by Andreas Müller about 1 month ago

  • Assignee changed from Andreas Müller to Katja Luther

#6 Updated by Katja Luther about 1 month ago

  • Assignee changed from Katja Luther to Andreas Müller

Tested for Structured DDS test:

  • select highest rank "Order", select lowest rank "species"
  • select highest rank "Genus" -> lowest rank still "species"
  • select highest rank "Subspecies" -> lowest rank removed.

#7 Updated by Andreas Müller about 1 month ago

  • % Done changed from 50 to 90

The problem itself is fixed now. There is a minor issue left: if a lowest rank is chosen the "Highest rank" combo still shows all ranks down to the lowest. So the filter works only for selecting first highest rank and then lowest but not the other way round. Please decide if this should be fixed here or if we add it to #9805 (issue 3 there is already about rank filtering)

#8 Updated by Andreas Müller about 1 month ago

  • Status changed from Resolved to Feedback
  • Assignee changed from Andreas Müller to Katja Luther

#9 Updated by Katja Luther about 1 month ago

Andreas Müller wrote:

The problem itself is fixed now. There is a minor issue left: if a lowest rank is chosen the "Highest rank" combo still shows all ranks down to the lowest. So the filter works only for selecting first highest rank and then lowest but not the other way round. Please decide if this should be fixed here or if we add it to #9805 (issue 3 there is already about rank filtering)

But if you choose the higher rank below the lowest rank, the lowest rank is emptied again, so it is not possible to create a wrong configuration, so I would move it to #9805.

#10 Updated by Andreas Müller about 1 month ago

  • Status changed from Feedback to Closed
  • % Done changed from 90 to 100

Ok, so I think we can close this ticket now. Or is there still an open issue?

#11 Updated by Andreas Müller about 1 month ago

  • Target version changed from Release 5.29 to Release 5.28

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)