fastruby / fastruby/points

Add relationship between "template story" and "client instance story"

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

还没有人认领这个 Issue。

Feature Request
主要语言
Ruby
星标
42
派生
17
PR 合并指标
30 天内没有已合并 PR

描述

**Before we start...:**

- [x] I checked the documentation and didn't find this feature
- [x] I checked to make sure that this feature has not already been requested

**Branch/Commit:**

main branch

**Describe the feature:**

Please include a detailed description of the feature you are requesting and any detail on it’s expected behavior.

> **As a user**
> **I clone a template story**
> **And then I add it to my client project**
> **And I see a relationship between the template story and the client instance story**

**Problem:**

Please include a detailed description of the problem this feature would solve.

> **As an admin**
> **I want to be able to keep a relationship between a template story and a client instance story**
> **So that I can later get insights from past upgrade projects**

**Resources:**

Let's say that there is a story (https://points.ombulabs.com/projects/181/stories/3334) in a template for a version jump (4.2 to 5.0) and I go ahead and clone that story for a new client project.

Then I would expect to see a relationship in the database that connects the template story to the instance story.

In the future, one would get insights from other client projects.

A person who is working on estimate an instance of https://points.ombulabs.com/projects/181/stories/3334 could talk to client project Acme's team and ask them about their experience with it.

**I will abide by the [code of conduct](https://github.com/fastruby/points/blob/main/CODE_OF_CONDUCT.md)**

贡献指南

这个仓库没有索引到贡献指南

从这里开始

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

调研方向

首先追踪 story 克隆流程,以及 template story 和 client instance story 的模型或数据库关系。完成的标准是,克隆操作会持久化两个 story 之间可查询的链接,从而支持所请求的未来 project insights;issue 中未指定任何文件或测试。

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

评估

技术栈
rails, ruby
领域
backend, databases
Issue 类型
功能
难度
5/5
预计耗时
一周以上
活跃度
停滞
描述清晰度
基本清楚
新手友好度
30/100

把新 issue 发到你的邮箱

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