Users seem to use the [Post your answer] as a reply often
@fenbox ya está trabajando en esto.
Desde el 11/3/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Context
I observe that users are often using the [Post your answer] as a reply to an answer, not understanding that this option is to answer a question. E.g. the following happens:
- User creates new question
- The question is answered, sometimes requesting for some more feedback if it does not solve the issue.
- The user has feedback, but instead of using the
[Add comment]option, he / she uses the[Post your answer]thinking it is to reply to the previous answer.
I think the reason is because the Your Answer form is immediately displayed, where the [Add comment] option requires an additional click to show the form. Thus users are missing that they are using the wrong form.
Examples:
- https://support.chirpstack.io/questions/10010000000000877/device-no-longer-receives-multicast-payloads
- https://support.chirpstack.io/questions/10010000000000872/chirpstack-does-not-receive-gateway-data
Describe the solution you'd like
Maybe an additional check should be added when the user of the question is the same as the user trying to press the [Post your answer]. Something like Only use this field to answer your own question. To reply to an answer please use the [Add comment] button.
Alternatively, maybe it should be made a bit "harded" to self-answer a question. E.g. when the user of the question and the user trying to answer is the same, do not show the Your Answer form but add a Button to expand it + making the user aware that it should only be used to answer the question, not to reply.
- Lenguaje dominante
- Go
- Estrellas
- 15.7k
- Forks
- 1.4k
- Merge medio
- 1 d 20 h
- PR fusionados (30 d)
- 6
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de apache/answer
-
List button click not working Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Hardening: cap the invite_user list size in UpdateQuestionInviteUser to bound notification fan-out Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
-
Gravatar hash is computed from the un-lowercased email, so mixed-case accounts render an identicon Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Todos los issues de apache/answer
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
bug group: validation priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
codecheckers/chekhov#51 ·
-
Creating worktree from an existing remote branch with a slash in it, has unexpected behaviour Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100