You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello everyone. This is my first issue in this project.
Is your feature request related to a problem? Please describe
We use a cloud-hosted Answer instance. It's common that some possible users do not even know the app and use another channel to ask something, like an issue in a project, for example, or just think something is a bug while it's not. We need a quick way to do a soft move, without forcing the user to rewrite everything.
Describe the solution you'd like
I think best experience for user would be having an admin endpoint to create the question as another user. So we can use it in workflows. It's already possible to have a user to create the question using the API, but it should be the asking user because he'll choose the right answer.
Hello everyone. This is my first issue in this project.
Is your feature request related to a problem? Please describe
We use a cloud-hosted Answer instance. It's common that some possible users do not even know the app and use another channel to ask something, like an issue in a project, for example, or just think something is a bug while it's not. We need a quick way to do a soft move, without forcing the user to rewrite everything.
Describe the solution you'd like
I think best experience for user would be having an admin endpoint to create the question as another user. So we can use it in workflows. It's already possible to have a user to create the question using the API, but it should be the asking user because he'll choose the right answer.
Describe alternatives you've considered
A simpler feature may be fill the new question form with query parameters, like "http://my-instance/questions/ask?title=Test%20Title&description=My%20%test%description&tags=mytag1,mytag2. This is a good feature in GitLab and GitHub while opening issues.
I can work in the solution if needed.
The text was updated successfully, but these errors were encountered: