Sample/Example Vault with Projects?

[mlevison]

I would love to see a sample vault, that used projects. I can't quite head wrapped around they work yet.

Irony, I teach Scrum and Kanban, for a living and I can’t quite wrap my head around projects here.

[renatomen]

Hi @mlevison

I'm one of the plug-in's contributors.

There's not much to know about projects in Task notes. The name "project" can be misleading because it means different things for different approaches and contexts.

• PMI Institude
• GTD (Getting Things Done)
• PARA method
• Personal Projects

It's a loaded word.

In Task notes, it is just field that indicates a parents-children relationship. Knowing when there are parents-children relationship allows the plug-in to render items in a tree structure, nested indefinitely. That's it.

TaskNotes doesn't make any assumptions.about what a "Project" means to the user. It's just a generic parent.

Each TaskNote can have multiple parents and multiple children. That allows the plug-in to show hierarchical relation that users can interpret based on their own frameworks and workflows.

Examples of hierarchies:

P. Task
C. |_ Subtask
ℹ️ To represent it in TaskNotes, the Subtask must reference Task in it's 'Project' field.

P. Epic
C. |_ Story
ℹ️ To represent it in TaskNotes, the Story must reference Epic in it's 'Project' field.

P. Program
C. |_ Project
ℹ️ To represent it in TaskNotes, the Project must reference Programe in it's 'Project' field.

P. Project
C. |_ Task
C. |_ Milestone

ℹ️ To represent it in TaskNotes, the Task and Milestone must reference Project in it's 'Project' field.

TaskNotes allows you to represent these relationships. It is up to you how to categorise your TaskNotes (how to define which notes are of type Subtask, project, task, epic bug etc).

You can use native obsidian tags in the "tags" property to determine the type or you could use a "type" property to store your predefined types.

In all example hierarchies alabove, TaskNotes only knows which are the parents and which are the children. By coincidence, instead of calling a parent "parent", TaskNotes names it "project", but from a user perspective not all elements in the (P.) lines are considered projects.

In my vault, the TaskNotes project field is mapped to the "in" property. Using the Epic example, it can be done like this:

P. Epic A (tags: #epic, in: empty)
C. |_ Story A1 tags: #story, in: Epic A)
C. |_ Subtask A1a (tags: #subtask, in: Story A1)

Let me know if you have more questions
Cheers

[mlevison]

It's funny, that was my guess. The problem is that the documentation never says anything explicit about projects, so I wasn’t sure. It felt like I was missing the key detail.

Projects - I'm about as far from PMI/GTD and even PARA, as you can get. I'm Certified Scrum Trainer by trade. An ongoing joke in my workshops - I would like the word 'Project' removed from the vocabulary of most teams, so it is ironic that I was asking about them here.