Project

General

Profile

Actions
Copy link

bug #9817

closed

AggregationWizard: Changing the maxRank results in empty minRank

Added by Katja Luther almost 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
New
Assignee:
Katja Luther
Category:
taxeditor
Target version:
Release 5.28
Start date:
Due date:
% Done:

100%

Estimated time:
Severity:
blocker
Found in Version:
Tags:
additivity fast aggregation

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.

Actions
Copy link
 #1

Updated by Andreas Müller almost 3 years ago

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

This is a regression therefore setting to 5.28

Actions
Copy link
 #2

Updated by Katja Luther almost 3 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 50
Actions
Copy link
 #3

Updated by Katja Luther almost 3 years ago

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

This should be fixed, please review.

Actions
Copy link
 #4

Updated by Katja Luther almost 3 years ago

  • Assignee set to Andreas Müller
  • Target version set to Release 5.51
Actions
Copy link
 #5

Updated by Andreas Müller almost 3 years ago

  • Assignee changed from Andreas Müller to Katja Luther
Actions
Copy link
 #6

Updated by Katja Luther almost 3 years 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.
Actions
Copy link
 #7

Updated by Andreas Müller almost 3 years 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)

Actions
Copy link
 #8

Updated by Andreas Müller almost 3 years ago

  • Status changed from Resolved to Feedback
  • Assignee changed from Andreas Müller to Katja Luther
Actions
Copy link
 #9

Updated by Katja Luther almost 3 years 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.

Actions
Copy link
 #10

Updated by Andreas Müller almost 3 years 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?

Actions
Copy link
 #11

Updated by Andreas Müller almost 3 years ago

  • Target version changed from Release 5.51 to Release 5.28
Actions
Copy link

Also available in: Atom PDF