Next steps for ConvDev

Conversational Development takes place for the majority place in the threads in issues and merge requests. I think we should actively explore to improve not only the large pieces and large features, but also the small details that make this so powerful.

One idea below and some related issues that I think fall under this idea.

Filtering comment and system notes

Right now, conversations and system messages are together and it's impossible to only focus on one of the two. It's fundamental to ConvDev that by default you see both, but some times you want to be able to focus on only one of the two.

My proposal is we allow you to easily toggle comments and system messages: both (default) / comments only / system messages only.

Make issue from comment

We've discussed this before (I can't find the issue), but sometimes it makes sense to split a conversation off by making a new issue from a comment.

We should link from the comment that became an issue directly, to indicate this.

Unread / read

Because everything becomes a linear timeline, it can be useful to have an idea of what you have or haven't read.

This can be a very heavy thing, both UI and performance wise, so if we do it, it should be very unintrusive and lightweight.

Related issues

• relationships between issues
• threads in issues

cc @gl-product