[Feature request] Project-controlling through collections and Roadmap

未關閉
#397 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
22/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
go
領域
backend, frontend

研究方向

This is a multi-part feature request covering roadmap collapse/expand, an iterations toggle, user indicators on roadmap items, and a row height offset fix. Start from the roadmap view in the Svelte frontend and the Go handlers that serve roadmap data, but the payload does not name specific files. Done would need the maintainers to agree on scope, since it bundles several separate changes.

由索引模型根據 Issue 內容生成。

描述

fixed-0.9.3

In our constellation we differentiate between two workspace types: client-space and product-space.

client-space has several epics with the work item type client-project and start and end dates. Those cluster the todos for this "project phase".

product-space has a few epics with the work item type internal-project with start and end dates. For the product-space we often use iterations to cluster items instead of creating an interal-project epic (depends on the scope and context of the project).

In theory we wanted to visualize what projects (internal and client) are currently overlapping to establish an overview that can be filtered by person - or used for planning (extending project phases, shortening them, delaying them etc, distributing sub-tasks throughout the epic phase)

To fully utilize this idea we need the option to:
  • collapse/expand all tasks feature like in the tree-view for roadmaps.
  • adding a toggle to enable iterations in the overview
    • Without the iterations in the roadmap we would need to create a dummy task for the iteration and script some automatic function that syncs the iteration items as child items of this card along with the dates
  • adding a user indicator to the roadmap item; referencing issue #285
  • fixing the height offset of item to timeline row
Image
主要語言
Go
星號
421
分支
50
平均合併
17 小時 34 分鐘
30 天內合併 PR
80

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

Windshiftapp/core 的其他 Issue

查看 Windshiftapp/core 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。