New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make thread reply notifications more visible #1230

tiltec opened this Issue Jan 23, 2019 · 2 comments


None yet
3 participants
Copy link

tiltec commented Jan 23, 2019

Currently, thread replies are in the "latest messages" menu listed below conversation replies:


This is not super obvious, as highlighted by this comment from Disa (Solikyl Gothenburg):

I think i understand the "summary of messages- place" now, and that it
is meant to do just what i was asking for. But its not really clear, ive
never seen the 'replies to threads-part' before in the usability-test,
because i dont scroll down under two months old messages to look for new
messages(now i know i should so its no longer a problem for me, but a
new person beginning to use karrot and looking for a summary of messages
will probably have the same problem).

We should think about a better way of presenting it, maybe have two tabs "conversations" and "threads" or just a hint that there are more notifications below.


This comment has been minimized.

Copy link

djahnie commented Jan 23, 2019

I like the tabs idea! Since we apparently will have tabs in the issues as well it makes sense to use them in more locations.


This comment has been minimized.

Copy link

brnsolikyl commented Jan 24, 2019

Tabs could be a good solution. I noticed a clear pattern from all of the usability tests we've done so far: people are confused by all buttons and notifications on the header. I think we need to tackle all of these problems together, and maybe try a bigger redesign for the next release. I'll try to sketch something...

We can do some usability testing on dev before we launch anything very new to production.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment