<!-- Actionable insights must recommend an action that needs to take place. An actionable insight both defines the insight and clearly calls out action or next step required to improve based on the result of the research observation or data. Actionable insights are tracked over time and will include follow-up. Please follow the tasks outlined in this issue for best results. Learn more in the handbook here: https://about.gitlab.com/handbook/product/ux/ux-research-training/research-insights/#actionable-insights This issue template is for an actionable insight that requires further exploration.--> ### Insight https://gitlab.com/gitlab-org/ux-research/-/issues/2201#insights * [Using a date range would be a good way to search for commits](https://gitlab.dovetailapp.com/projects/6wpZZIqkyLniu0IasXpjZN/insights/present/6DrR3N9ZcFBQBnHQb8y1GH) ### Supporting evidence > Generally the squads that I work with commits like every day, like five sec, six, 10 commits per day. We have really this religiously commit culture after we implement some new brand new future and new button, we just commit it. We would expect to filter exactly the day that we worked the most and get exactly the commits that we made and not seeing actually all of the list of commits because there are a lot of commits there that are being made every day. So I really expect a filter here where could filter exactly to that commit. ### Action <!--Since this is an actionable insight that requires further exploration, ensure the action is algned to that. Describe the next step or action that needs to take place as a result of the research. The action should be clearly defined, achievable, and directly tied back to the insight. Make sure to use directive terminology, such as: conduct, explore, redesign, etc. --> Explore design and technical feasibility of searching commits with a date filter ### Resources <!--Add resources as links below or as related issues. --> - :dove: [Dovetail project](https://gitlab.dovetailapp.com/projects/6wpZZIqkyLniu0IasXpjZN/readme) - :mag: [Research issue](https://gitlab.com/gitlab-org/ux-research/-/issues/2201#insights) ### Tasks <!--Fill out these tasks in order to consider an Actionable Insight complete. Actionable Insights are created as confidential by default, but can be made non-confidential if the insight does not include information about competitors from a Competitor Evaluation or any other confidential information. --> - [ ] Assign this issue to the appropriate Product Manager, Product Designer, or UX Researcher. - [ ] Add the appropriate `Group` (such as `~"group::source code"`) label to the issue. This helps identify and track actionable insights at the group level. - [ ] Link this issue back to the original research issue in the GitLab UX Research project and the Dovetail project. - [ ] Adjust confidentiality of this issue if applicable