16

Changes to the flag dialog have been made. However, I can't help but feel that the job was rushed, as many things have been left untouched, resulting in inconsistencies between old and new elements:

  • The "Not an answer" option on the answer flag dialog looks terribly out of place:

    I think this answer should be...

    • deleted as spam

    • deleted as rude or abusive

    • Not an answer

    • ...

    It is the only option with a remaining capital letter, and it doesn't work with the initial phrasing ("I think this answer should be Not an answer").

  • The "This question belongs on another site in the Stack Exchange network" flag is found under "closed" -> "A community-specific reason". While it made sense when "closed" was "Needs improvement", it's no longer correct: I don't want the question closed, I want it migrated to another site.

    (One might argue that from the system's perspective, migration means closing and duplicating the question, but we're users, we speak human, we can't be expected to guess how SE's backend works)

  • The Help Center wasn't updated: it still mentions the old options' names (same on SO, and I assume most if not all sites)

    Considering the flag dialog changes are network wide, it should be up to employees to update help centers accordingly with the changes they made.

  • There are two paths to flagging as a duplicate ("closed as a duplicate question" and "closed" -> "Duplicate")

    This was already a thing before the flag dialog changes, but well, it's worth rementionning.

  • After selecting "closed", the next dialog reads:

    What kind of improvement does this question need?

    ...even though the option I clicked is named "closed" and no longer "Needs improvement".

  • The wording is inconsistent, while the first dialog for questions and answers is worded as such:

    This is the beginning of the sentence, and this is...

    • the first possible ending of the sentence

    • the second possible ending of the sentence

    • ...

    The other dialogs are left untouched, keeping their original wording:

    What option will you go with?

    • Option A

    • Option B

    • ...

    Please keep it consistent. Maybe could the "What kind of improvement does this question need?" dialog be changed to something like:

    This question needs to be closed because...

    • it is a duplicate

    • of a community-specific reason

    • it needs details or clarity

    • it needs more focus

    • it is opinion-based

    To fit the new wording style. The opposite can also be done (and personally, I'd prefer that) by restoring the original wording style to the first dialog (honestly, not having a capital letter at the start of every option looks really bad.)

: I'd like to know which of these points the community cares about and which they don't or feel are fine as-is. If you have more things to raise, please point them out, I'll gladly add them to this post!

I see most of these problems as "due to a mistake". Clearly, not enough time was put into this, and it is SE Inc.'s mistake for not properly testing these changes and make everything consistent and coherent.

Gives a whole new meaning to "Community Asks Sprint". "Sprint" doesn't mean you need to complete it as fast as possible without caring nor testing.

1 Answer 1

5

Thank you for bringing these things to our attention. We are working on the bug fixes, and the Help Center article changes are also in the process of being updated.

As far as the inconsistencies with the Flag dialog vs the Closed dialog, that change was out of scope for this sprint. If we want to update the closed modal dialogs, that would be a discussion with the rest of the community to come to a consensus, as they did with the flags and closed post notices.

8
  • 2
    Thank you for your answer. Thing is, I wished the bug fixes, the Help Center articles and other things I pointed out were fixed before the change went live. I can hardly see how could developers not see these problems when changing the flag dialog, and it's not like there was any need to rush this either. As for the "closed" dialog, if it's out of scope, but is highly important to make what is on scope look good, wouldn't it have made sense to ask the community first and make changes afterwards? It's frustrating, there were good ideas and intentions behind this, but it feels rushed... Commented Jun 27 at 13:51
  • 5
    Our flagging system has a lot of paths that are integrated throughout the system. Sometimes the issues with the changes are not obvious until they go live, and that is why I requested specifically if there is an issue; please let us know so we can fix it. Bugs, while unfortunate, do happen, and we work very hard to fix them expeditiously as we did in this instance. As for the Help Center articles, as things were still in flux with the language (bug fixes and edits for clarity), I wanted to wait until those fixes were pushed before I updated it.
    – Bella_Blue StaffMod
    Commented Jun 27 at 14:09
  • 3
    Regarding the "closed" flag dialog, we are not proceeding with any changes to it at this time because such adjustments require community consensus before implementation. Since there was no prior discussion or agreement within the community for that change, modifying the dialog falls outside the project's scope. If you feel that a change is necessary, I encourage you to start a discussion on Meta to gather input and reach a community decision.
    – Bella_Blue StaffMod
    Commented Jun 27 at 14:32
  • @Bella_Blue Have you just changed the flag dialog? i.sstatic.net/xVeG3x4i.png from Super User is an example where "very low quality" appeared under both "deleted as rude or abusive" and "deleted as very low quality". However, just went to open the dialog again to check and the text "very low quality" no longer appears. Commented Jun 27 at 15:15
  • 2
    @ChesterGillon Yes we are in the process of making changes as per community request.
    – Bella_Blue StaffMod
    Commented Jun 27 at 15:21
  • 1
    @Bella_Blue Thanks for confirming, I won't then raise a new question about seeing "very low quality", now that seems to have been resolved. Commented Jun 27 at 15:23
  • @Bella_Blue "such adjustments require community consensus" Would the score of 16 on this post constitute consensus? If not, what score would? I don't expect this post to reach the hundreds like the original flag dialog changes feature request did, but I'm not sure at what point can something be considered as community consensus by today's standards. "I encourage you to start a discussion on Meta" This very post is tagged [discussion], I'm afraid writing a separate post would make it a duplicate of this one. Commented Jun 29 at 13:16
  • @RedStoneMatt you are welcome to add a feature request tag to the post.
    – Bella_Blue StaffMod
    Commented Jul 10 at 15:33

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.