Timeline for Updating the "code not implemented or not working as intended" community-specific close reason to use the new five-field close reason system
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 1, 2022 at 13:19 | answer | added | Toby Speight | timeline score: 1 | |
| Mar 27, 2022 at 18:56 | comment | added | gparyani | @Mast There is another significant benefit. Right now, any question closed with an off-topic sub-reason will simply show to the vast majority of users (without enough rep to vote to close stations) that they were closed as off-topic. There's no explanation shown to those users why the question is off-topic, which leads to confusion, especially with questions that appear to relate to the site's general scope. Revamping these reasons to the latest system will show the post notice close description (field 3) to all users, making it so they can see why exactly the question is not in scope. | |
| Mar 27, 2022 at 16:32 | comment | added | Mast Mod | For completeness: the current wording is used in all fields. The only difference between 'post owner guidance' and 'privileged user guidance' today is that the latter shows who closed the question while the former does not. Both guidances show the exact same text as the text in the flag dialog does. Currently none of our close reasons use the new format, the old ones will still be supported. The primary benefit of the new systems is being able to give specific advice when it's useful. Editing the reasons will require a CM and will be retroactive. | |
| S Mar 24, 2022 at 3:05 | answer | added | gparyani | timeline score: 0 | |
| S Mar 24, 2022 at 3:05 | history | asked | gparyani | CC BY-SA 4.0 |