Hi Thomas:

In message <1573023745.09.0.541804250831.issue2550926@roundup.psfhosted.org>,
Thomas Arendsen Hein writes:
>Related to this:
>
>- I often create issues that I assign to myself. Here the status
>  "unread" doesn't apply, because I already read it.

Well the status doesn't make any sense in this use case. So maybe
change the 'unread' status to 'new' in the db and make a corresponding
change in the detector.

>- Users often create issues without assigning them to anyone, because
>  it is not their job to do that. When I'm assigning the issue e.g.
>  to ber with a comment like "Bernhard, can you take care of this?"
>  This sets the status from unread to chatting, but the one who would
>  do the real work on the issue did not read it.

If you put Bern on the nosy list, and then make the update he will see
it right? But I see what you mean, he will get the "Bern can you take
care of this" message not the original opening message. In my tracker
when the assignedto is changed, an email with the first and last three
messages is sent to the new assignedto person.

>  Or a second user would say "I have the same problem", causing the
>  status to be set to chatting.
>  So my question is: Should chatting (optionally) only be set if the
>  message is sent by the person in the assignedto field?

I don't know about that. We have a number of discussions going on in
the roundup tracker that have no assignedto party. Note the tracker
uses new, open etc not unread, but if it were to use unread, the first
response from sombody would still be a chat. I can see your assignedto
requirement being valid business logic though. Especially if the first
employee who responds to an issue gets assigned.

I think these would be good examples for the wiki.