Caseflow: Move case search bar to navigation bar
Move case search bar to the navigation bar to make more room in the container for subsequent Caseflow functionality.
Mocks
Resources
laurjpeterson
All 15 comments
@amprokop thoughts on this?
laurjpeterson
on 26 Apr 2018
Could be sweet. Questions —
- Will this be consistent across apps? Seems like it should at least appear across Reader and everything Queue-related. What about Hearing Prep? Certification?
- How does this rank among alternatives — potentially we could have a "Search" link or a search icon link at the top which takes the user to a search page. Tradeoff— it's one extra click, but potentially a lot less clutter. Not sure if the search bar in the header adds some level of distraction
- With the search bar embedded in the header, how do we think about navigation back to what the user was previously doing before searching? If we want to have some sort of breadcrumb/back link, it probably needs to be programmatically named
amprokop
on 26 Apr 2018
Just a quick note the search functionality could vary, based on what works best for each caseflow feature/product:
- full search bar
- only search icon that is expandable on click
- only search link that takes user to search page on click
mkhandekar
on 26 Apr 2018
I think it could be consistent across apps, though probably not Certification or Dispatch just yet. I recommend we keep it to Board users for now. Do you see any drawbacks of it being across all apps? If we moved the search bar like in this ticket, will it inherently affect all apps or can we keep it to queue?
Would defer to @sneha-pai and @mkhandekar on the other design suggestions. I haven't done user research on the alternatives. The main goal for moving the search bar right now is to make more space for the Judge functionality we're working on, and pave the way for future users.
How does moving the search bar change the navigation from how it is done today, when the search bar is just below the header?
laurjpeterson
on 26 Apr 2018
Currently the search bar is only visible on a handful of pages, with this change would we have the search bar available on every page?
lowellrex
on 26 Apr 2018
With this particular ticket, I’m not proposing it be changed from what we have today.
laurjpeterson
on 26 Apr 2018
from how we have it today*
laurjpeterson
on 26 Apr 2018
Hmm can we get a sense of what the medium term view is re: where this bar should appear, @laurjpeterson?
If we definitely want it to appear eventually in other React apps other than Queue (Reader, Certification, for instance), than that may affect the implementation of this ticket. I'm thinking the eng who picks this up might want to design the solution in a way that allows us to easily enable this search bar across different Caseflow apps/pages, not just for this page.
amprokop
on 28 Jun 2018
Our (Queue team) current thinking is to have the search component in the nav bar everywhere on Caseflow:
... and when a user clicks on that, they are taken to Caseflow Search landing page.
But we need to talk through this with other teams as it will affect:
- what do I see when I search for something from Queue?
- what do I see when I search for something from Reader?
- and I'm sure other questions I am not thinking of right now!
We have it in our design team priorities to work through navigation & search throughout Caseflow (to and from other products) in the next couple weeks and would definitely want to make sure the engineer who would be working on this is part of those conversations @amprokop.
cc: @sneha-pai @allyceh
mkhandekar
on 28 Jun 2018
Thanks for everyone's thoughts! Was thinking about the subtleties here and I didn't find it easy to disentangle how we would roll this nav bar out to all apps from a wider Case Search rollout, so I captured an idea for how that might happen to try to move this task forward. Caveat that I don't know if folks have made alternative plans yet, so apologies in advance if there's already a fleshed out path there, and let's chat!
@lowellrex @mkhandekar @sneha-pai @laurjpeterson, feel free to take a look at https://github.com/department-of-veterans-affairs/caseflow/issues/6111
amprokop
on 5 Jul 2018
The idea described in @amprokop's new issue works for me / @lowellrex.
@laurjpeterson did you get a chance to take a look?
Adding that when we implement this, let's also deal with the empty/white space that was caused by removing breadcrumbs (https://github.com/department-of-veterans-affairs/caseflow/pull/6201).
mkhandekar
on 12 Jul 2018
yes! apologies for my delay. i am good with alex's plan.
laurjpeterson
on 13 Jul 2018
hi @amprokop + @laurjpeterson! y'all met a couple weeks ago about this right? can one of you post a super quick update about the feasibility of this change?
mkhandekar
on 13 Aug 2018
@mkhandekar we're all aligned on this change and @amprokop's proposed implementation! however, since search functionality is working (though not the most up to date design), and with @mdbenjam heading out for a few weeks, we're going to postpone implementing it. @lowellrex will focus on organizational queues and vso work for this sprint.
laurjpeterson
on 13 Aug 2018
closing this issue in favor of https://github.com/department-of-veterans-affairs/caseflow/issues/6111, where implementation details are captured.
laurjpeterson
on 14 Aug 2018
Related issues
hschallhorn
·
4Comments
laurjpeterson
·
4Comments
lomky
·
3Comments
leikkisa
·
4Comments
laurjpeterson
·
5Comments
Most helpful comment
@mkhandekar we're all aligned on this change and @amprokop's proposed implementation! however, since search functionality is working (though not the most up to date design), and with @mdbenjam heading out for a few weeks, we're going to postpone implementing it. @lowellrex will focus on organizational queues and vso work for this sprint.