Create sub-todos / todo events
When you have an active todo for a target (typically an issue or an MR), you won't get a new todo for that same event.
However, it would be very handy to know:
- How many times todo-creating events have been issued on that target. (In general, the higher, the more important.)
- Which todo was most recently bumped.
- If a todo of a 'regular' type (mention) was later superseded by an 'important' type (build failed, assigned, etc.).
This means that we could allow sorting todos on
updated_at, but we'd also show the todo if a filter on type matched any of the types in the sub-todo / todo events table. I think we could use some UX here, but I understand how the backend would work, at least
This replaces #23293 (closed).