Design: Define scope of work for renaming to-dos to notifications

Problem

We will transition to using the word "notification" in the product instead of "to-do". We are doing this for two reasons:

1. The existing to-do list has relatively low customer adoption. When interviewing customers about this, we found that they didn't expect to find notifications in a "to-do list." When showing them the functionality that was there, the noted that it did meet many of their needs – they just would have never discovered it on their own.
2. The existing to-do list is not a to-do list: it does not provide any of the functionality users expect in personal task management software – features like creating new to-dos and breaking down existing ones, setting dates and priorities, and collaborating with others via comments and assignment. By freeing up the name "to-do", we give ourselves space to explore offering that sort of functionality in the future, possibly building on top of custom work items.

This will involve cross-stage changes, like updating the sidebar on issues and merge requests. Given the potential disruption these changes could cause to users, we will bundle these changes into a single public release. Once this goes live, we will market the change as "introducing web notifications".

Proposal

We'll need to define what changes will be in scope for this effort, and how things will work and look after this change.

WIP Figma file