Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
This is a current limitation of the software. Right now, there is simply no way to add detailed feedback to the close reason. There is a list of pre-written close reasons (which can be set per site...
Answer
#1: Initial revision
## This is a current limitation of the software. Right now, there is simply no way to add detailed feedback to the close reason. There is a list of pre-written close reasons (which can be set per site). If you feel like there is an issue with the wording of a close reason, then feel free to suggest wording changes in a new post (ex. [this one on Meta](https://meta.codidact.com/questions/277447)). ## Changes are planned See [luap42's post](https://meta.codidact.com/questions/278229#answer-278233) on *What are the close reasons on Codidact?*. From that post: > If I recall correctly, the future close system will be based on three groups of problems with posts: > > 1. **Duplicates.** > 2. **Off-topic.** This includes every post that isn't suitable for a site. If a community should ban easy questions, "too easy" would fall under this entry. Off-topic posts are inherently *unfixable*. > 3. **Needs author's attention.** These posts can be fixed but need attention from the author, because not everyone can do so (for example: missing information). > > For the groups 2 and 3, the sites will be able to define sub-reasons (such as: "opinion based" under off-topic or "unclear" under needs author's attention). It might be possible to support the selection of multiple problems for these groups, or at least group 3.groups, or at least group 3. Once those future changes are in place, close notices should be much clearer. With the ability to select multiple close reasons, we can make individual close reasons more specific. > So ... can we find a better way to give feedback when closing a question? If you're asking about methods, then comments are probably the best way to give feedback, since it allows for discussion on why it was closed and how to improve the question. If you're asking about what we, the givers of feedback, can do, then there isn't much that we aren't already doing, or trying to do. As you said, sometimes the feedback doesn't entirely succeed in explaining the close reason, but if that happens all we can do is have them ask for clarification. --- ## Miscellaneous > > This post contains multiple questions or has many possible indistinguishable correct answers or requires extraordinary long answers. > > That lists 3 different reasons for closure, leaving it unclear which one applies to the question. > > Also, the second possible reason is not conveyed clearly, because "many possible indistinguishable answers" does not make grammatical sense: if the answers are indistinguishable, they are duplicates - why is that a fault of the question? This would probably do better as a separate question on Meta. The way I see it, just ignore the "indistinguishable" - i.e., "This post has many possible (different) correct answers." This overlaps with both "too broad" and "too subjective," if there is no way to distinguish which answer is correct, then the question is unanswerable.