True Sub-Cards - Parent/Child Relationship with Status
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
True Sub-Cards (Parent/Child Relationship with Status)
Feature Request
I frequently find myself missing a true parent-child relationship between cards in Nextcloud Deck. Which limits the efficiency of task management IMHO.
Requested Features:
1️⃣ Batch Creation of Child Cards
- Within a card, provide an option to quickly create multiple sub-cards in a streamlined flow.
2️⃣ Easily Assign Parent-Child Relationships
- Provide a clear GUI flow to manually define relationships. E.g. "Is Child of" "Is Parent of" options after click on cards action button in overview.
3️⃣ Sub-Card Status Visibility
- Display the status of all sub-cards within the parent card for better tracking and progress overview. E.g. in a new tab named "relations" where a list with the sub-cards is visible and their status is shown.
Why This Is Needed
This feature would greatly enhance workflow organization.
It is not the same as:
- Creating a new list
- Breaking out into a new board
- Using tags
- Adding a checklist inside a card
- Randomly linking cards in the bodytext (where no status is communicated nor the relation is visible on both entities)
Those workarounds do not provide the structured hierarchy needed for proper project and task breakdowns. I have reviewed existing issues but found none that directly address this request precisely—hence, I am submitting this as a new feature suggestion.
Would love to hear thoughts on feasibility and interest from others! 🚀
Use may want to use [👍] / [👎] below
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the card overview and card action button flows, then consider how a relations tab could expose parent and child cards with their statuses. The requested scope includes batch child creation, manual relationship assignment, and status visibility; done would require all three parts to work as a consistent hierarchy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100