• Type: Feature Part
• Resolution: Fixed
• Priority: L3 - Default
• Fix Version/s: 3.0.0-alpha2, 3.0.0
• Affects Version/s: None
• Component/s: frontend
• Labels:

  None

This is the controller panel for Smart Panels app

[OPT-3136] Implement the new redesigned date filter

Collapse comment: Michael Schoettes added a comment - 11/Feb/20 11:50 AM

Michael Schoettes added a comment - 11/Feb/20 11:50 AM

I've spotted two minor issues affecting the date filter:

Issue #1: when editing a fixed date filter the input fields show today's date and not the value of the date filter

Problem: when changing the end date of the filter the start date will be set to today's date and vice versa.

Expected  Behavior: Input fields show the correct filter value

Issue #2: I can enter extreme large number which cannot be handled by the backend

Problem: when adding a filter for last .. custom number days it is possible to enter an extreme large number like 1e+92 days which results in an endless loading spinner

Expected behavior: the input filed has an upper limit or the user gets feedback that his filter value is too big.  **

Expand comment: Michael Schoettes added a comment - 11/Feb/20 11:50 AM

Michael Schoettes added a comment - 11/Feb/20 11:50 AM I've spotted two minor issues affecting the date filter: Issue #1 : when editing a fixed date filter the input fields show today's date and not the value of the date filter Problem: when changing the end date of the filter the start date will be set to today's date and vice versa. Expected  Behavior: Input fields show the correct filter value Issue #2 : I can enter extreme large number which cannot be handled by the backend Problem: when adding a filter for last .. custom number days it is possible to enter an extreme large number like 1e+92 days which results in an endless loading spinner Expected behavior: the input filed has an upper limit or the user gets feedback that his filter value is too big.  **

Collapse comment: Michael Schoettes added a comment - 18/Feb/20 2:17 PM

Michael Schoettes added a comment - 18/Feb/20 2:17 PM

There is still a small glitch when entering big values for the rolling date filter:

Problem: When I add a rolling start date filter for the last 99999999 days the report shows no data to display, although the respective request returns the same response as requests with lower value (1000 days). Same applies for all other units.

Expected Behavior: I see all instances started in the last 99999999 days

Expand comment: Michael Schoettes added a comment - 18/Feb/20 2:17 PM

Michael Schoettes added a comment - 18/Feb/20 2:17 PM There is still a small glitch when entering big values for the rolling date filter: Problem: When I add a rolling start date filter for the last 99999999 days the report shows no data to display, although the respective request returns the same response as requests with lower value (1000 days). Same applies for all other units. Expected Behavior: I see all instances started in the last 99999999 days

Collapse comment: Omran Abazeed added a comment - 20/Feb/20 4:32 PM, Edited by Omran Abazeed - 20/Feb/20 4:32 PM

Omran Abazeed added a comment - 20/Feb/20 4:32 PM - edited

It turned out to be a backend issue: 
Reproduce: 

• Create a line chart report, grouped by start-date
• Add rolling start-date filter with value of 99999999 days
• The report evaluation response returns data although there the instance count is 0

Expand comment: Omran Abazeed added a comment - 20/Feb/20 4:32 PM, Edited by Omran Abazeed - 20/Feb/20 4:32 PM

Omran Abazeed added a comment - 20/Feb/20 4:32 PM - edited It turned out to be a backend issue:  Reproduce:   Create a line chart report, grouped by start-date Add rolling start-date filter with value of 99999999 days The report evaluation response returns data although there the instance count is 0

Collapse comment: Johannes added a comment - 20/Feb/20 4:47 PM

Johannes added a comment - 20/Feb/20 4:47 PM

I think this bug should not be part of this feature implementation. I created the follow-up bug ticket OPT-3136 for it and will close this issue now.

Expand comment: Johannes added a comment - 20/Feb/20 4:47 PM

Johannes added a comment - 20/Feb/20 4:47 PM I think this bug should not be part of this feature implementation. I created the follow-up bug ticket OPT-3136 for it and will close this issue now.