Sub-cards?

[Grunthos]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.

Sometimes is is nice to have a taks broken into sub-tasks, each with dues dates and notes etc.

Describe the solution you'd like

The ability to link cards hierarchically, eg.

Migrate to new ISP:

• Move DNS
• Move mail
• Move Web Server
• Decommission old server

One might argue that this is a 'project', but one might need a third level of hierarchy:
Move Mail

• Select shortlisy of new storage backend candidates
• test backed performance
• select final candidate
• configure and test migration script for new backend

etc

Describe alternatives you've considered

It seems that one needs a structure like:

Board
   List
      Card
         List...

** Additional Notes **

Kanban has the concept of subcards, but I think sub-lists might work a little better.

[stefan-niedermann]

Have you tried the task syntax

- [ ] Item 1
- [x] Item 2

which will result in

• Item 1
• Item 2

and resulting being visible at the card like this:

Edit: I just read that this won't cover your requirements like due dates...

[stefan-niedermann]

Searching the issues resulted in a duplicate of #1818

This issue was marked as a duplicate of #272 which has been closed with the following comment of the maintainer:

As this sounds like a nice feature, the requests for this are quite low. Currently there are no plans to implement such a feature. Thus I will close this ticket for now. This does not mean we don't want this feature, but it is simply not on our roadmap for the near future. If somebody wants to implement this feature nevertheless we are happy to assist and help out.

If you wish to have this feature implemented by the Nextcloud GmbH there is the option for consulting work on top of your Nextcloud Enterprise subscription to get your features implemented.

[Grunthos]

Damn! I did a search for sub and sub-card etc. But not 'group'!

At least I'm not alone in my interest in this feature.

[stefan-niedermann]

No problem 🙂 @juliushaertl is currently at vacation, let's wait and see how he thinks about it. Personally (as maintainer of the Deck Android app) i can see that this would cause maintenance efforts which are not to underestimate. Therefore we should think hard about implementing (and maintaining) this feature or not.

[Grunthos]

Depending on where you see the maintenance issues, it might be sufficient to have an interface that shows:

Migrate to New Server
    3 Sub-tasks ((perhaps in a list))

Then, clicking on '3 sub-tasks' would just take to you a whole new list (one step down in the hierarchy, with prior tasks hidden); no need to display the whole hierarchy.

One might go so far as to have:

Migrate to New Server
    Sub-task 1
    Sub-task 2
    Sub-task 3

With an arbitrary long list on the card, then clicking on any of them takes you to the relevant (previously hidden?) BOARD(?)...in that way, you could have 'Triage', 'In Progress' etc for the sub-tasks.

Or it perhaps just hides the higher level of the tree as suggested above, but displays the tasks with the same lists as the main board.

I agree it's complex...and I don't know where your maintenance complexity lies. Any solution that gets a usable hierarchy would be great.

[putt1ck]

AFAICT the hierarchy you are asking for exists by use of checklists on a card as described above, or use of lists when a due date is needed for the sub tasks.

[Grunthos]

@putt1ck Not really, unless lists and checklist items canhave names, dates, comments and notes like a card.

I probably should not have presented the dummy UI above -- it was an attempt to sidestep design complexitie, and may have resulted in the wrong impression about what I am asking for (per the first post).

[putt1ck]

Lists have subitems that are cards. So when we have a complex project we split up the boards; the groupings of the cards are then done with lists.

[Grunthos]

Yes...but what I am asking for is cards to have lists UNDER them, I suppose. I thought that's what you were suggesting in your first post.

I have a fairly traditional (I think) arrangement of lists: #Triage, #Todo, #OnHold, #Inprogress etc

On those lists, I have cards. As per my discussion above, I want to break those cards down into smaller (yet still complex and hence needing it's own card) activities.

Does this make sense? I have this feeling that we are talking at cross-purposes.

[putt1ck]

The scenario you describe is where we would break out the card into its own board/list, where list headings would be the "meta card"

[Grunthos]

Does that actually work though? Don't you then need to construct 'In Progress', 'Review', 'Complete' lists for each of these cards?

[juliushaertl]

I think having a way to add a different board or stack as a "meta-card" makes sense, similar to how github does it:

However it is not on the roadmap currently.

[muppeth]

Have you tried the task syntax

• Item 1
• Item 2

@stefan-niedermann This is already quite cool solution. Would be good to make it into GUI somehow so people not familair with markdown (or not even knowing they can pull this off on deck) will be able to do it? I think, although not entirely covering the issue at hand would already solve people looking for similar solutions (like me as i got here exactly looking for something like that).

[hitam4450]

@stefan-niedermann Great idea to get started with using markdown much easier....

[Grunthos]

I have already addressed why @stefan-niedermann 's solution is not fit for purpose: lack of due dates, lack of ability to add them to other lists etc. ie. they are NOT cards....

[aproposnix]

I have already addressed why @stefan-niedermann 's solution is not fit for purpose: lack of due dates, lack of ability to add them to other lists etc. ie. they are NOT cards....

Hi Grunthos... so if I understand correctly, you want something like this:

[Grunthos]

Sorry, @aproposnix , didn't see your response until now!

I guess that would be close, but I would then want to do anything with those sub-items that I can do with a card: assign it to a person, put it on another list (eg.. "Stalled", "ToDo", "Review") etc etc. It's hard to tell from your UI image exacttly what can be done with the "tasks". Are they fully-fledged cards?

[rolandixor]

The solution of "meta" cards, similar to what Github has, seems like a great approach to this issue, imho.

Separately, it would be useful to have a simple UI (could maybe be implemented with an existing JS, O/S markdown plugin) for adding checkboxes or other formatting.

[ocervell]

Any updates here ? Would love to see that feature land, let me know how I can help :)

[daudtivan]

To contribute to the point: I'm using Deck to run brainstorming and innovative workshops with my clients, where ideas and contributions come and go in any direction.

Participants create new cards on the fly as discussions progress during the brainstorming session with anything that comes to their mind. There is absolutely no structure for this exercise. The purpose is to collect ideas, which result in many, many cards.

Once the brainstorming is over several ideas look alike or are simple duplicates, so we need to group similar or complementary ideas. One card is elected to become the "master" of an idea, while others will be its "childs" in a group or hierarchy.

I can't anticipate the hierarchy or grouping, so inner tasks as proposed above can't help in such situations. Tagging to group cards is a more complicated alternative, but can take me there (at the cost of some patience and time). Naming it a project is incorrect, as it must be voted/approved before it becomes one.

I hope you guys go on with grouping/linking deck cards. Would facilitate my life quite a lot.

[x29a]

Does this discussion go in the same direction as this forum post? Because i wondered the same, why not use the same data structure as the Tasks app, just be a different (kanban style) view for it.

The columns would then rather be tags, i guess, or seperate lists?! So that the subtask is free for actual tasks of a card (which would be subcards if i understood the discussion above and in linked items correctly)? With all of their properties and functionality.

[SjoerdV]

you can even

1. have sub-sub-tasks by using the markdown syntax as follows -> use 4 spaces before the 'sub-sub-task'

* [x] sub-task 1
    * [x] sub-sub-task 1
* [x] sub-task 2

rendered like:

• sub-task 1
  • sub-sub-task 1
• sub-task 2

2. add a new line for sub-task preserving indent, but do not create a new sub-task -> use 2 spaces after the last character in the sub-task

* [x] sub-task 1  
extra comment on new line
* [x] sub-task2

rendered like:

• sub-task 1
  extra comment on new line
• sub-task2

[borisrunakov]

Using MD for sub-task works, however if subcards were implemented, one could set due date, comments and relationships for each subcard respectively

[SjoerdV]

Using MD for sub-task works, however if subcards were implemented, one could set due date, comments and relationships for each subcard respectively

@borisrunakov I am wondering what the functional difference would be between cards and subcards? Maybe you want a way to organize cards and put them on a timeline or something like that?

I think that would transform Kanban style back to PRINCE2 😉

UPDATE: this analysis didn't do right to all the efforts people already put into this issue, so please disregard. The comment below has a nice overview of examples

[rolandixor]

@SjoerdV I'm confused as to what hasn't been made clear about this in other comments?

Examples were given here #2103 (comment), here #2103 (comment), here #2103 (comment), here #2103 (comment), and more.

The use case and functional differences have been repeatedly explained by multiple commenters in multiple ways. I'm not trying to be sarcastic here. I'm just genuinely not understanding what is being missed here?

[Kiendeleo]

A practical example of this would be something like:

Primary Card: Delpoy New Server (Assigned to a team with an estimated completion date)
Subtasks:
Purchase New Server (Assigned to purchasing with a due date)
Receive New Server and add to inventory (Assigned to Receiving with a due date)
Provision server (Assigned to IT with a due date)
Deploy in Rack (Assigned to IT with a due date)
Migrate Database (Assigned to Database Admin with a due date)
etc...