Create questions for another user

未关闭
#1,184 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 6 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
go
领域
api, backend

调研方向

未指定文件或测试。首先检查现有的问题创建 API 以及管理员操作的授权路径;完成这项工作需要确定范围,并编写覆盖所选工作流的测试,包括谁可以为其他用户创建问题。

由索引模型根据 Issue 内容生成。

描述

new-feature

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.

主要语言
Go
星标
15.7k
派生
1.4k
平均合并
9 天 6 小时
30 天内合并 PR
8

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

apache/answer 的其他 Issue

查看 apache/answer 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。