Idea #3235
Updated by Tom Clegg almost 10 years ago
For this sprint, focus on functionality inside the search box rather than achieving the best UI behavior. * Search button in top nav brings up a modal. * Typing in the search query text box and hitting Enter (or clicking the Search button) updates search results. * Search for (in order): projects, collections, pipeline templates, pipeline instances, jobs. * Row of checkboxes just below query text box determines which object types are shown in results. * Click to highlight a row/result. * Type "Escape" or click "close" button to dismiss the modal. * Click "Open" button (at bottom of modal) to open the selected result. * (Optional?) Control-click "Open" button should open in a new window. Making it a link rather than a button/input element should be enough to get this with default browser behavior. * (Optional?) Click a caret to expand a project in the results pane and show contents of the project. This should be implemented with a generic calling mechanism just like the existing chooser -- perhaps it can be an extension of the existing chooser, using a SearchController and a query parameter (@models[]@?) that determines which model types should be shown/searched. When it has enough capabilities, we'll use it to replace the chooser modal entirely. For example, when choosing a collection, the chooser will support "type a project name, click to expand the project, and select a collection from that project" instead of the existing "choose a project from the drop-down list, then type to search collections in that project". Defer for next phase: * Ensure control-click "Open" button opens in a new window. Making it a link rather than a button/input element should be enough to get this with default browser behavior. * Click a caret to expand a project in the results pane and show contents of the project.