Combined and customized todos and notifications
- GitLab has todos and email notifications.
- They should be combined because:
- There is a lot of overlap in functionality. Further development in both means wasted effort and poor user experience and poor product management.
- A todo vs a notification is ill-defined. One person’s notification is another person’s todo. For example, one person may care about all created Discussion issues (notification) but another person may need to triage all of them and always leave at least a comment (todo).
- GitLab should not define which events are notifications vs todos. GitLab should provide the tools, but not impose the workflow. Personal workflows are highly different and customized. Therefore, we should not presume. Being @mentioned may be a notification to one person, but could be a todo to a different person.
- GitLab should give that customization ability to individual users. GitLab shouldn’t even make a distinction/definition of notifications and todos.
- GitLab defines all events. For example, issue created with Discussion label is an event. Being @-mentioned is a different event.
- For each event (or group or events), you as a user choose:
- Should GitLab email me about the event happening?
- Should GitLab create a dismissible object for me to manage in the Web UI?
- This design can be iterated towards since we already have a mechanism to send emails about events and a mechanism to create dismissable objects. We just have to generalize the concepts a little bit.