Prevent accidental deleting

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

还没有人认领这个 Issue。

评估

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

调研方向

该 issue 没有提到任何文件、测试或入口点。首先确定项目需要删除权限、归档、软删除,还是这些方式的组合,然后跟踪现有的项目和故事删除流程。当所选方案能够防止或恢复误删除,并且已针对项目和故事两者完成验证时,即视为完成。

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

描述

Feature Request

https://ombulabs.atlassian.net/browse/DT-251

IMPORTANT: please make sure you ask yourself all intro questions and fill all sections of the template.

Before we start...:

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

Branch/Commit:

main

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 add a project that I which to use as some sort of template project
And then I add all the stories with descriptions
I don't want anyone to accidentally delete the template project (since it cannot be recovered)
I don't want anyone to accidentally delete a story in my template project (since it cannot be recovered

Problem:

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

As a user
I add a project with stories
So that I can use the project as a template to be cloned for future projects
Now I or anybody on my team can delete the project
And I or anybody on my team can delete stories in the project
There is no way to prevent projects or stories from being deleted
There is no way to recover a project or story after it has been deleted

Ideas:

I see two possible solutions, we can discuss implementing either or both.

  1. A permission scheme that prevents unauthorised deletion.
  2. Prevent deleting all together, use a different mechanism such as archiving or rejecting
  3. Allow soft deleting only so we can recover projects and stories.

I will abide by the code of conduct

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

贡献指南

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

从这里开始

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

fastruby/points 的其他 Issue

查看 fastruby/points 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

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