Skip to content
This repository has been archived by the owner on Jan 14, 2022. It is now read-only.

Filters are not always working and overall experience is terrible #773

Closed
ghost opened this issue Jul 18, 2018 · 4 comments
Closed

Filters are not always working and overall experience is terrible #773

ghost opened this issue Jul 18, 2018 · 4 comments
Assignees
@MichalTuleja
Labels
bug frontend *hard
Projects
Version 2.1.5 Sprint Board 27-08-18 Version 2.2.0 Sprint Board 10-12-18

Comments

@ghost
Copy link

ghost commented Jul 18, 2018

Try out a filter like 'Min' and enter the value 1 it will not work.

The overal experience with the filter menu is terrible (tested in Chrome and Firefox). The screenshot is just one example. Please make it more snappy and user-friendly.
image
@MichalTuleja MichalTuleja added this to Open Issues in Version 2.1.5 via automation Aug 28, 2018
@MichalTuleja MichalTuleja added this to New Issues in Sprint Board 27-08-18 via automation Aug 28, 2018
@MichalTuleja MichalTuleja added this to the Version 2.1.5 milestone Aug 28, 2018
@lsilvs
Copy link
Contributor

lsilvs commented Sep 3, 2018 •
edited

The Min issue mentioned is related to a core api issue (see LiskHQ/lisk-sdk#2358)

Other issues were addressed on this PR #806

@lsilvs lsilvs closed this as completed Sep 3, 2018
Version 2.1.5 automation moved this from Open Issues to Closed Issues Sep 3, 2018
Sprint Board 27-08-18 automation moved this from New Issues to Closed Issues Sep 3, 2018
@punkr0ck
Copy link

Why is this closed? Filters don't work. It never shows correct data.

@ghost
Copy link
Author

ghost commented Sep 13, 2018

Agreed. Just 2 random examples:
image
image

@ghost ghost mentioned this issue Sep 13, 2018
Closed
@lsilvs
Copy link
Contributor

lsilvs commented Sep 13, 2018

As mentioned here #773 (comment) the Min and other combinations of filters are related to a core api issue (LiskHQ/lisk-sdk#2358)

The second one mentioned above was addressed in this PR #818. More precisely, in this commit d952e3c

I agree it doesn't make sense to close the issue if it's not entirely fixed. I'll reopen and it should be closed when the Core issue is fixed ;)

@lsilvs lsilvs reopened this Sep 13, 2018
@MichalTuleja MichalTuleja added this to To Do in Version 2.2.0 via automation Sep 13, 2018
@MichalTuleja MichalTuleja removed this from the Version 2.1.5 milestone Sep 13, 2018
@lsilvs lsilvs removed their assignment Oct 23, 2018
@MichalTuleja MichalTuleja added this to New Issues in Sprint Board 10-12-18 via automation Dec 7, 2018
This was referenced Dec 10, 2018
Closed
Closed
@MichalTuleja MichalTuleja self-assigned this Dec 10, 2018
@MichalTuleja MichalTuleja mentioned this issue Dec 12, 2018
Merged
Version 2.2.0 automation moved this from Open Issues to Closed Issues Dec 18, 2018
Sprint Board 10-12-18 automation moved this from New Issues to Closed Issues Dec 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@MichalTuleja MichalTuleja

Labels
bug frontend *hard
Projects
No open projects
Sprint Board 10-12-18
  
Closed Issues
Sprint Board 27-08-18
  
Closed Issues
Version 2.1.5
  
Closed Issues
Version 2.2.0
  
Closed Issues
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lsilvs @MichalTuleja @punkr0ck