[Feature request] Project-controlling through collections and Roadmap

Offen
#397 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
22/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
go
Bereich
backend, frontend

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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
Vorherrschende Sprache
Go
Sterne
421
Forks
50
Ø Merge
17 Std. 34 Min.
Gemergte PRs (30 T.)
80

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus Windshiftapp/core

Alle Issues in Windshiftapp/core

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.