I’m VERY new to fibery. I’ve read that you can create sub tasks but I haven’t been able to figure out how. Can someone help me out?
You can share with us some details about your use case and I would be glad to record an explanatory video for you
Polina will certainly give you more details and direct help, but if you want to experiment in the meantime: what I’ve done is create a “Sub-task” Type, with a Relationship to the “Task” Type, so you can specify 1 or more sub-tasks in a Task Type. You can also just create a “self” Relationship to the Task Type, but you like me may not prefer how this ends up being represented (it means you end up with two additional fields on the Task type, one for “incoming” relation, one for “outgoing” relationship). I encourage you to experiment with it to see how it works.
I agree with @Oshyan about experimenting, and I’d add that the decision about whether sub-tasks should use a self-relation or a new type probably depends on whether the task and sub-task share the same properties or not, and also whether you want multi-layers (sub-sub-tasks etc) or not.
Also, if you do choose to have a one-to-many self-relation, then you will notice that of the two fields that are created, one is a collection (the children) and one is just a single-entity field (the parent). You can name them appropriately to minimise confusion.
Thanks for the tips guys. I’ll experiment as you suggest @Oshyan.
@Chr1sG I am interested in sub-sub-tasks. Ideally, I’m looking for a system that would allow for infinite nesting of sub-tasks. Given that, which approach would you suggest?
@Polina_Zenevich My use cases are extremely varied. I’m looking for a system within which I can organize the goals and projects of my entire life, ranging from the usual tasks of daily life, to my career goals, various personal/career projects ranging from writing to podcasting to vfx production, and any business ventures I undertake. I’m looking for something that can support deeply nested and varied organizational and project structures and within which I can plan and manage all of this within time periods of hours to 20 and more years. I have looked at probably 30 or more project management solutions and have yet to find one that seems up to the task.
A good analogy for the kind of system I’m looking for would be to imagine I was the dicator of a country who wanted to use this system to plan out his country’s future and manage all of its activities. I want a system that can be used to run many organizations with varied goals and tasks, that are nevertheless connected by a singular vision and whose activities can be coordinated and interconnected.
BTW - one downside to fibery that I’m encountering is that it appears that its different apps can only exist at the root of the entire structure. Ideally, I’d like to be able to have multiple instances of these apps, each one dedicated to and nested within the organization to which it applies. At a glance, it appears that smart folders can be used to affect something of this functionality, but I’m not sure how robust that option is.
@Chr1sG thanks for the tip about renaming the two fields created when self referencing tasks.
Do you any of you know of a way to view tasks with their sub-tasks indented below them? And with a drop-down button to control the visibility of sub-task levels?
If you need multiple layers of nesting, I suggest creating a relation from the task type to itself, using a one-to-many relation (assuming that ‘child’ tasks can only have one ‘parent’ task, but a parent task can have multiple children).
You will probably find hierarchical lists a good way to represent the multiple nesting (they’re pretty similar to smart folders in behaviour, and they’re no longer a beta feature ).
@Chr1sG The list view doesn’t appear to support self-referencing types. All I get are the top-level tasks that I setup. There is no drop-down button available to display the tasks children.
… Actually, it doesn’t work with a one to many relationship between different types either.
Nevermind - I got it working. Though it’s kinda lame that it doesn’t automatically populate the children levels… Actually, it does in the case of self-referencing tasks if you click on the circle-arrow option “group by the same type relation”
The beauty of Fibery is its flexibility. In some cases, each type might have relations to multiple other types, so Fibery doesn’t second guess which of these the user might want showing in the hierarchical list.
Fair point. Though, it would be useful to have an “auto populate children” button.