nextcloud / nextcloud/deck

Add an attribute to cards that logs the dates they move between different stacks

Open
#5,345 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: activity feature: api
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

Hello Nextcloud Deck Team,

I'm an avid user of the Deck feature, particularly its Kanban-style boards (ToDo, InProgress, In Review, Completed). I've noticed a potential area for enhancement that could significantly improve task management and tracking efficiency.

Feature Request:
I'm creating a Gantt chart view using the Deck API to visualize the duration it takes to complete tasks. This would be particularly beneficial for understanding the time spent on each task. Currently, while the Kanban boards provide an excellent overview of task status, they lack the ability to track and display the duration each task takes from start to completion.

Implementation Idea:
The Gantt chart could utilize data from the 'Completed' stack to indicate when a task is finished. However, for this to be truly effective, it would also need to track when a task moves from 'ToDo' to 'InProgress' (signifying the start of the task) and from 'In Review' to 'Completed' (signifying task completion). This would offer a comprehensive view of the task lifecycle.

One potential way to achieve this could be by adding an attribute to cards that logs the dates they move between different stacks. This data can then be used to populate the Gantt chart.

I believe this feature could greatly enhance the functionality of Deck, making it an even more powerful tool for project management. I would appreciate your consideration of this feature request and am eager to hear your thoughts on its feasibility.

Thank you for your continuous efforts in improving Nextcloud Deck.

Best regards,
Ernesto

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Deck API's card and stack behavior, focusing on how movements between stacks are represented. Define what transition dates cards should expose and verify that the resulting data supports tracking a card from ToDo through completion for Gantt chart use.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.