Being able to embed/nest a specific node/tree from a different list would definitely streamline project management in Checkvist.

Still holding out hope for this feature. The ability to effectively embed nodes within other lists, symlink style so that they're the same data element and are "synced" (i.e. if someone edits the sub-items in the Node which is in list A, those edits will also show up in the identical Node which is embedded in list B since it is one and the same Node, just displaying in two places). I think it would be a real killer feature.

This is a fantastic idea. It makes a lot of sense for collaboration, e.g. if you are building up a complex knowledge document. Different team members could work on different areas of research, and then a master document could be composed just using inline, dynamically embedded outlines.

Somebody mentioned that this might bloat Checkvist into a full-on project manager, but I disagree. This feature need not have any significant effect on the software design, or your workflow, if you opt not to use it.

+1 for this one. my use case: I often have hard time deciding whether to have items as subitems of 'xx' them into separate lists.

Really, they are often subitems of a big list. But that big list may have so many items that organizing it becomes very painful. When I find an item I want to move, I then need to search for the parent item I want to move it under. So I end up 'xx'ing the parent items, so they can easily be moved things under. But here I lose flexibility: I now have to move explicitly to the new lists to view their contents, and they are now out of context.

So being allowed to show contents of a linked list inline would help me get the best of both worlds: give me quick move targets 'inside' the current list, and see everything in context.

I would like to expand on this great (and under-appreciated) feature: this could be used to create a "master" Checkvist that referenced all one's other Checkvists. Why? The "master" checkvist could have a description of the purpose and context of each checkvist and/or a summary.

I would encourage Checkvist to highlight this great capability!!

"Yes, please!" to nesting. The ability to subset one list into another would really compliment the extract feature, and I could really use it right now for creating summary lists that I can then share selected pieces (the extracted/nested parts) with others

Thanks everyone for the comments and suggestions for this feature.

So far, I cannot name any estimates when we will start working on this - but definitely not before the coming winter. Not because we don't consider it important - but because there are more important tasks we have to solve.

Thanks again,
KIR

This would be the killer feature that makes checkvist better than all other. There is the feature of focusing, but that would sort of require many of my lists to be moved to a single list. And it doesn't allow sharing sublists, like previously described.

Kirill asked to merge the other feature request, so adding my notes & use case to this thread for public comment/feedback:

Embed existing lists/sublists, not just hyperlinks (similar to symlinks)

Rather than simply linking to a list/sublist, which embeds a hyperlink in my existing list, a real killer feature would be to actually embed that sublist in my current list. This would be have a lot like a symlink, with the key feature being that if I edit something in the sublist that edit is reflected everywhere in Checkvist that that sublist appears.

Example use case: If I am listing out travel ideas by Geography as follows:
- Italy
--- Wine tasting
- Puerto Rico:
--- Caving
-------- Tour operators information
-------- links
-------- other information specific to puerto rico caving, etc
--- Scuba Diving
--- Beaches
... etc

And I also have another bucket list, which is organized around Activity Type as follows:
- Natural Wonders
- Rafting trips
- Caving trips
- Diving trips
- Sailing trips

What I would really love to be able to do, is embed the Puerto Rico Caving sublist (in the 1st list above - Geographies) into the "Caving" section of the second list (Activity Types) above. This allows me to enter more information and flesh that sublist out further, regardless of whether I'm currently thinking along Geography or Activity Type. Changes are reflected in both.

At a meta-level, this allows lists to go beyond 1 "hinge" of data. I can effectively organize my information across 2 criteria/dimensions, rather than being limited to 1 (I can organize specific information about caving in Puerto Rico so that it appears on my list of travel ideas organized by Geography as well as my list of travel ideas organized by Activity Type). More generally, this allows massive flexibility.

It will also form the backbone to some pretty amazing sharing features. For example, I could share a sublist with someone and instead of them having to view it as a "list", they could actually move it around within their own list structures. Maybe I share a specific Todo list with someone (i.e. fix site CSS) which has multiple sub-tasks. Instead of having to view this as a full list, they can actually take this and move it around their todo list (however they may organize it). Since all it really is, is a symlink to my subtask-list, any edits they or I make will sync.

Workflowy implemented something similar to this, focused only on sharing. They allow you to share a sublist with someone, and for them to move that sublist around in their own hierarchy with ease. What they have not implemented and what could be extremely interesting, is sharing that same sublist with yourself. This would allow you to move it around your own lists and hierarchy, so that even if a list item should appear in multiple places you don't have to duplicate it.

Implementation-wise, the only real hairy piece is circular references. I Imagine this is a nightmare for workflowy since their users just have one big mega-list. However, for Checkvist, it could actually be very easy: don't allow people to embed/symlink any lists of sublists within one List. Only allow symlinking/embedding sublists across separate Lists (full list objects).

In my opinion, this is the single last thing Checkvist would have to do to be a full-fledged collaboration tool (and not just an awesome individual tool). It allows people to share "todos", but not just full lists. If you get your data structure to support this, it will all me to, for example, share a task, including subtasks, (from a big project-list) with someone and allow them to organize it how they like within their own organizational system.

There are times where sharing an entire "project" or List with someone is what you want. There are other times when sharing a Todo (task) from that list is what you want. It also enables you to embed a sub-tree across multiple Lists, and have changes synced.

I think this may be similar to an idea I just created, which can be found here: http://checkvist.uservoice.com/forums/2121-general/suggestions/3713589-embed-existing-lists-sublists-not-just-hyperlinks

The idea is to allow a sublist to be embedded elsewhere in Checkvist. Changes to the sublist or it's children are reflected anywhere this sublist is embedded.

Profound implications for sharing, organizing, and de-duping across checkvist. Would love to hear whether this is what the original post of this idea intended, or something else. And, of course, what the checkvist developers think about it!

My idea is similar to a feature workflowy just implemented, which can be found here
http://blog.workflowy.com/post/31422897499/embed-shared-workflowy-lists-in-your-own-account

Unfortunately, this task is not in our nearest plans.

We consider implementing Zoom feature before this one: https://checkvist.uservoice.com/forums/2121-general/suggestions/898937-zoom-and-view-features

We also plan to provide a possibility to allow easy linking between lists:
https://checkvist.uservoice.com/forums/2121-general/suggestions/1045559-easy-linking-to-existing-lists-and-tasks

After four years, is there any ETA for this task?
Also thanks for this excelleant application, keep it development.

Also mentioned in http://checkvist.uservoice.com/forums/2121-general/suggestions/2307093-allow-embedding-lists-not-just-link-

Depending on how this is implemented, this feature could be a duplicate of: http://checkvist.uservoice.com/forums/2121-general/suggestions/898937-zoom-and-view-features?ref=title

This is a great idea, and would improve the usefulness of CheckVist immensely. Please see WorkFlowy (www.workflowy.com) for a beautiful rendition of this concept.

This concept also allows very elegant sharing features, as you could share just a branch of a large tree. This branch would show up as a full list (just a zoomed in view) for the sharee. What this means is that you could share at any level.

In general, the way WorkFlowy deals with sharing and "zooming" is brilliant. I love everything else better about Checkvist, but LOVE those features in WorkFlowy. If you were able to combine them it would be truly powerful.

I think the link to another checklist is a good solution for this. Does that not solve it?

agree with the above - too much nesting just overcomplexifies what is already "simply functional".

This is a great idea, but can be very complex. If you don't keep it real simple, you'll soon have a full-blown project manger, with all the issues. Does the world need Y.A. MS Project?