I believe that the "mark comment as spam" storage needs to be unique to the user, rather than storing it as issue.spam_state (i.e. you can't identify it per user).
As it is currently, other users see whether someone else has marked it as spam, which I believe is confusing.
This is how I see it working:
When Alice clicks "notify" then it should display "notified as abuse" on the issue/comment. (The user can also come back to the same page later and click an [x] to cancel the notification.) When Bob views the issue/comment then it displays as normal. If Bob then clicks "notify" then because that's a second person then the issue becomes hidden - maybe it still displays to him and Alice, or maybe it disappears for them too and Bob gets a flash message telling him "notified as abuse".
When we have moderation #27 , any issue/comment that has one or more people having pressed "notify" for it, goes into the moderation queue for the sysadmin.
I believe that the "mark comment as spam" storage needs to be unique to the user, rather than storing it as issue.spam_state (i.e. you can't identify it per user).
As it is currently, other users see whether someone else has marked it as spam, which I believe is confusing.
This is how I see it working:
When Alice clicks "notify" then it should display "notified as abuse" on the issue/comment. (The user can also come back to the same page later and click an [x] to cancel the notification.) When Bob views the issue/comment then it displays as normal. If Bob then clicks "notify" then because that's a second person then the issue becomes hidden - maybe it still displays to him and Alice, or maybe it disappears for them too and Bob gets a flash message telling him "notified as abuse".
When we have moderation #27 , any issue/comment that has one or more people having pressed "notify" for it, goes into the moderation queue for the sysadmin.