### Release notes <!--What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). "--> You can now snooze notifications in your to-do list, allowing you to temporarily hide items and focus on what's most important right now. Whether you need an hour to concentrate or want to revisit a task tomorrow, you'll have fine-grained control over when notifications reappear, helping you manage your workflow more effectively. ### Problem to solve * Team leads are often involved in concurrent discussions on issues, epics, and merge requests. * Sometimes they get a notification about something they want to follow up on, but don't have time to do so right now. * They want to save the notification so they can be reminded to return to the topic when they have time. ### Proposal As we're iteratively transforming the to-do list into a notification list, we'll introduce this functionality within the current to-do list by: * Adding a button to snooze to-dos * Providing a list of common durations to snooze the to-do: * For one hour * Until later today (4 hours later) * Until tomorrow (tomorrow at 9am local time) * Providing an option for custom snoozing duration (by time and date) * When snoozing a to-do, it should be removed from the main list of to-dos * When a snoozed to-do reaches its alarm time, it should reappear in the main list * Users can only snooze a to-do once. Snoozing the to-do again should only change the alarm time for the to-do * Show snoozed to-dos on a separate tab * To-do counts should exclude snoozed notifications ### Design Adding a snooze button to the existing to-do list would look as follows: | To-do list page | Snooze dropdown | Custom time/date picking | Snoozed tab | Full time stamp in tooltip | Snoozed item returned to main list | |-----------------|-----------------|--------------------------|-------------|----------------------------|------------------------------------| |  |  |  |  |  |  | [Figma](https://www.figma.com/design/cwJZWpMESEW2YeCXm7tXzo/Snoozing-%2317712?node-id=6911-185138&t=7ukDwTOE1mzRhW1o-1) // [WIP prototype](https://www.figma.com/proto/cwJZWpMESEW2YeCXm7tXzo/Snoozing-%2317712?node-id=8368-68046&t=hmF7X2wR2VmWpyTV-1&scaling=min-zoom&content-scaling=fixed&page-id=6911%3A185138&starting-point-node-id=8368%3A68046) ### Intended users * [Parker (Product Manager)](https://handbook.gitlab.com/handbook/product/personas/#parker-product-manager) * [Delaney (Development Team Lead)](https://handbook.gitlab.com/handbook/product/personas/#delaney-development-team-lead) ### Feature Usage Metrics * % of active users that snooze a notification in last 30 days * Weekly user retention for snoozing notifications * Completion rate for snoozed notifications? ### Does this feature require an audit event? No, this is user-level data. It does not impact behavior at the instance, group, or project level. ### Implementation plan #### Database - [x] Add the following columns to the `todos` table: | Column name | Type | Default value | Notes | |-------------|------|---------------|-------| | `snoozed_until` | `timestamp without time zone` | None | It holds the date and time when the todo will be moved back to the todos list. This gets reset whenever the set time is reached, which has the effect of moving the todo out of the `Snoozed` tab and back to the list. | #### API - [x] Implement the GraphQL mutation for snoozing a todo: ```graphql mutation TodoSnooze($todoId: ID!, $snoozedUntil: Time!) { todoSnooze(id: $todoId, snoozedUntil: $snoozedUntil) { errors } } ``` - [x] Implement the GraphQL mutation for un-snoozing a todo: ```graphql mutation TodoUnSnooze($todoId: ID!) { todoUnSnooze(id: $todoId) { errors } } ``` - [x] The `todos` query should return the todos sorted by `snoozed_until` _and_ `created_date`. #### Backend - [x] Create a `snoozed` scope that returns todos where the `snoozed_until` timestamp is set to some time in the future. - [x] Create a `not_snoozed` scope, or update the `pending` scope to return todos where the `snoozed_until` timestamp is not set, or set to some time in the past. - Whether we decide to create a new scope or piggy-back on the existing `pending` one, we'll need to keep an eye out for todos counters. They should still be in sync with the todos standard tab. - [x] The `snoozeTodo` mutation handler should perform the following: - [x] Set the `snoozed_until` column to the `snoozedUntil` parameter (UTC). - [x] Create the `unsnoozeTodo` mutation handler. - [x] It will be called when users manually "un-snooze" a todo. - [x] It resets the `snoozed_until` columns. #### Frontend - [x] Add a `Snooze` disclosure dropdown to each todo item in the list. - [x] Refer to the designs for the actions that should be implemented. - [x] Keep the times dynamic. Eg, if the todos dashboard has been left opened for an hour, times displayed and set to the API should still be relative to the current time. - [x] Implement the custom snooze date and time modal. - [x] Both the modal and the disclosure trigger the `snoozeTodo` GraphQL mutation. See **API** section for the parameters. - [x] Implement the `Snoozed` todos tab. - [x] It lists todos from the `snoozed` scope. - [x] Todo items show when they will be moved back to the list `Snoozed until...`. A tooltip shows more details on the snooze time (hour, time zone). - [x] A button lets users move the todo back to the list by triggering the `unsnoozeTodo` GraphQL mutation. - [x] ~~The `Mark as done` button is here too, it triggers the `todoMarkDone` GraphQL mutation.~~ (this is being superseded by https://gitlab.com/gitlab-org/gitlab/-/issues/16564). #### Follow-up tasks from code reviews From https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175117#note_2277691962: - [-] Revisit the timestamps' display as per the linked comment. (moved to https://gitlab.com/gitlab-org/gitlab/-/issues/523019) - [-] Resolving a todo keeps it visible till the auto-refresh kicks in, but snoozing a todo hides it immediately... Could we also keep it around, to keep things consistent? (moved to https://gitlab.com/gitlab-org/gitlab/-/issues/523019) - [x] When (un)snoozing, the _Pending_ counter in the tab doesn't update. - [x] Resolving a todo should `null` its `snoozed_until`.