Skip to content
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

Treat Basic / Text Search Forms as First Class Components #4276

Closed
bdeining opened this issue Jan 29, 2019 · 4 comments
Closed

Treat Basic / Text Search Forms as First Class Components #4276

bdeining opened this issue Jan 29, 2019 · 4 comments

Comments

@bdeining
Copy link
Member

Description

Treat Basic / Text Search Forms as First Class Citizens. With the introduction of custom search forms, these were moved under the search form management view, which created a poor user experience since the user would have to click more to conduct a search.
[Description of the issue]

Expected behavior:

[What you expect to happen]
The Basic / Text Search forms should be available from the initial dropdown.

Actual behavior:

[What actually happens]
The Basic / Text Search forms are buried in an additional dropdown.

Version

[Application version]
2.14

Additional Information

Any additional information, configuration or data that might be necessary
to reproduce the issue.
Original PR that introduced the poor UX changes : #3004

@coyotesqrl coyotesqrl added this to To do in GH Issues Pilot Test via automation Jan 30, 2019
@mojogitoverhere
Copy link
Contributor

This has been fixed in #4227

@coyotesqrl
Copy link
Member

Should this be closed, @mojogitoverhere?

@mojogitoverhere
Copy link
Contributor

@coyotesqrl yes

@coyotesqrl
Copy link
Member

OBE: Resolved with #4227

GH Issues Pilot Test automation moved this from To do to Done Jan 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Development

No branches or pull requests

3 participants