Timeline for Moderator flag dashboard design refresh (alpha)
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 29, 2019 at 14:19 | comment | added | Wrzlprmft | @BrianNickel: It seems like this includes the auto low-quality flag, which does not fall into the category of “flags where it does not make any difference whether you mark them as helpful or decline them”, as marking them as helpful comes with an auto-downvote (and this seems to be what happens if you choose resolve). I would just get rid of this auto-downvote altogether. | |
| Jun 27, 2019 at 17:24 | history | edited | Brian NickelStaffMod | CC BY-SA 4.0 |
added 3 characters in body
|
| Jun 27, 2019 at 17:24 | comment | added | Brian Nickel StaffMod | I've implemented single-click resolve for auto flags. If all flags on a post are auto flags, the "Resolve all flags" dropdown button becomes a "Resolve all flags (auto)" button. Otherwise, the single flag resolve buttons (Helpful... and Decline...) become "Resolve (auto)". I don't love the naming there, but I'm keeping it consistent with the other button for now. | |
| Jun 10, 2019 at 9:53 | comment | added | Discrete lizard | After being able to look at the previous behaviour again, it seems this is not new. Still, I do wonder why this field appears for community auto-flags. | |
| Jun 10, 2019 at 9:49 | comment | added | Discrete lizard | In particular, if I mark a community auto-flag as helpful, it asks for a comment. I don't think anyone is ever going to read that comment, so that step is unnecessary and confusing. I also think that it didn't ask for a comment on auto-flags previously (which I would be able to check if not for caching). @BrianNickel is this covered by this feature request or should I make a new post? | |
| May 30, 2019 at 17:02 | history | edited | Brian NickelStaffMod | CC BY-SA 4.0 |
added 20 characters in body
|
| May 30, 2019 at 17:01 | comment | added | Brian Nickel StaffMod |
We already have logic that does this for invalid flags (FlagTypeId = 12) but I'm not really sure what code (if any) creates these flags. I'll add this to the list for a design review. Maybe if the button says "Resolve all flags (auto)" or something, it'll help.
|
|
| May 30, 2019 at 15:11 | comment | added | User that hates AI | @Catija I think Stack Exchange isn't doing something with Community's flag data anyway. So you could theoretically replace Helpful/Decline with a simple Okay or Dismiss button. | |
| May 30, 2019 at 14:49 | comment | added | Catija StaffMod | There's a UX concern that we have behavior be predictable. Single-click deletion of one "user's" flags (Community) is surprising, particularly to mods who don't see them often. As someone who started declining Community flags with silly reasons because they were annoying me... I know the feeling... finding a way to ... do something with them more quickly would be useful... :) | |
| May 30, 2019 at 14:41 | comment | added | Wrzlprmft | @Catija: Do you see the "Helpful… | Decline…" next to the flag? – Yes, but it’s not very prominent (which may be considered another problem). Still, this may be a good opportunity to improve this. | |
| May 30, 2019 at 14:40 | comment | added | Catija StaffMod | Do you see the "Helpful… | Decline…" next to the flag? That gives you the same two-click handling. The "resolve all flags" is designed for multiple flags on the same post which you want to handle the same way. | |
| May 30, 2019 at 14:20 | history | answered | Wrzlprmft | CC BY-SA 4.0 |