### Problem to solve As part of https://gitlab.com/groups/gitlab-org/-/epics/2114, we are building out a more robust log explorer functionality. As part of our new log explorer, we will want to include the ability to filter logs by time period. We will need to discuss what time options we'd like to have available. Do we want a set of default options available to users (ex, show last 15 minutes, 1 hour, 1 day) or do we want more robust time filtering options available? ### Intended users <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. * [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager) * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Presley (Product Designer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#presley-product-designer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) * [Sam (Security Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sam-security-analyst) * [Dana (Data Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#dana-data-analyst) Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ --> ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> ### Proposal This issue has been broken down into two iterations. This issue will address the first iteration. In this iteration, we will be adding another dropdown to the log view so that users can filter by time. It will look like this:  The second iteration will be covered in https://gitlab.com/gitlab-org/gitlab/issues/37983 and scheduled for a later release (currently set for %"12.8") <details> #### This is the previous proposal notes for reference For the first pass, we can offer a series of defined options for the users. In later iterations, we can consider a more robust time/date picker. If we add a time dropdown to the filters and search bar that are being discussed in https://gitlab.com/gitlab-org/gitlab/issues/37425#note_253530405, it would look something like this:  During implementation, we'll likely need to consider: * The length of the dropdowns. The decision here will be dependent on whether or not the container has a fixed or a fluid width. * How this view re-sizes for different screen sizes. A preferable way forward would be to first implement filtered search, which will avoid the two issues highlighted above. If we are able to implement filtered search first, the design would be updated as follows: | If we can get all filters into the search bar | If environment still needs to be a separate dropdown | | ------ | ------ | | |  | Which direction we proceed in will depend on the level of engineering effort required. </details> ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?--> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements If this feature requires changing permissions, this document https://docs.gitlab.com/ee/user/permissions.html must be updated accordingly. --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further help: https://about.gitlab.com/handbook/engineering/quality/test-engineering/ --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### What is the type of buyer? <!-- Which leads to: in which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> ### Links / references