-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default global filter for status in search #3124
Labels
Comments
VassilIordanov
changed the title
Default filters for search
Default global filter for status in search
Aug 4, 2020
VassilIordanov
added a commit
that referenced
this issue
Aug 5, 2020
VassilIordanov
added a commit
that referenced
this issue
Aug 5, 2020
VassilIordanov
added a commit
that referenced
this issue
Aug 5, 2020
VassilIordanov
added a commit
that referenced
this issue
Aug 5, 2020
VassilIordanov
added a commit
that referenced
this issue
Aug 5, 2020
VassilIordanov
added a commit
that referenced
this issue
Aug 5, 2020
VassilIordanov
added a commit
that referenced
this issue
Aug 5, 2020
gjvoosten
added a commit
that referenced
this issue
Aug 5, 2020
Make sure migration has a unique name. Properly quote camelCased columns. Use correct boolean type depending on database. Remove text seemingly pasted at random.
gjvoosten
added a commit
that referenced
this issue
Aug 5, 2020
gjvoosten
added a commit
that referenced
this issue
Aug 5, 2020
gjvoosten
added a commit
that referenced
this issue
Aug 5, 2020
gjvoosten
added a commit
that referenced
this issue
Aug 5, 2020
These search query beans are used in batching and have non-primitive fields that need to be cloned.
VassilIordanov
added a commit
that referenced
this issue
Aug 5, 2020
gjvoosten
added a commit
that referenced
this issue
Aug 5, 2020
gjvoosten
added a commit
that referenced
this issue
Aug 5, 2020
It is no longer an array, as the NEW_USER choice is gone, so having multiple values is pointless.
gjvoosten
added a commit
that referenced
this issue
Aug 5, 2020
gjvoosten
pushed a commit
that referenced
this issue
Aug 5, 2020
gjvoosten
added a commit
that referenced
this issue
Aug 5, 2020
gjvoosten
added a commit
that referenced
this issue
Aug 5, 2020
It is no longer an array, as the NEW_USER choice is gone, so having multiple values is pointless.
gjvoosten
added a commit
that referenced
this issue
Aug 5, 2020
gjvoosten
added a commit
that referenced
this issue
Aug 5, 2020
Implemented in release 2.1.27-285 on 11 August 2020. Closing the ticket. |
VassilIordanov
added a commit
that referenced
this issue
Aug 18, 2020
VassilIordanov
added a commit
that referenced
this issue
Sep 1, 2020
… not present Also, make AnetDevAuthenticator behave the same as AnetAuthenticationFilter - by not setting the domain username as name
VassilIordanov
added a commit
that referenced
this issue
Sep 1, 2020
…ts and report attendance selection UIs
VassilIordanov
added a commit
that referenced
this issue
Sep 1, 2020
gjvoosten
added a commit
that referenced
this issue
Oct 20, 2020
gjvoosten
added a commit
that referenced
this issue
Oct 20, 2020
gjvoosten
pushed a commit
that referenced
this issue
Oct 27, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When users type a search text to search for something, the search finds both active and inactive items. The default path should be to see only active items, unless explicitly specified.
It would be more intuitive to have a default search filter present, which is for
status=active
. If the user wants to see anything beyond that, they can either explicitly remove the filter, or specify a different value for status.The issue is that not all search types have an status attribute, and one of them (People) has 3 different values:
Report - no status attribute
People - status is one of ACTIVE, INACTIVE, NEW_USER
all others - status is one of ACTIVE, INACTIVE
One solution is to make:
Report - no status attribute
all others, including people - status is one of ACTIVE, INACTIVE
People - use pendingVerification instead for deriving NEW_USER state
Subsequently, we can add a global filter for status (with a UI default of ACTIVE), and (for now) with no effect on reports. Alternatively, we could make it equivalent to state=PUBLISHED for reports
The text was updated successfully, but these errors were encountered: