Refer to a task by id in different files as a super or sub task.

[blueeaglex]

⚠️ Please check that this feature request hasn't been suggested before.

• I searched previous Ideas in Discussions didn't find any similar feature requests.
• I searched previous Issues didn't find any similar feature requests.
• I am only requesting a single feature. Multiple changes should be split into individual requests, with links between them.
• I believe my requested feature will be generally applicable to other users, not just me: it is not uniquely tied to my personal workflow.

🔖 Feature description

As we know, a task can refer to another by id using 'depends on by id' like this :

- [ ] MySubTask ⛔ em8yay

Why don't offer a specifier to define the detail type of the dependency, such as sub depends or supper depends?

✔️ Solution

Offer a specifier to define the detail type of the dependency.

❓ Alternatives

No response

📝 Additional Context

No response

[claremacrae]

Hi @blueeaglex, thanks for making a suggestion.

There isn't enough information here to understand what exactly you are proposing and why it would be important to implement it.

Please have a look at the following:

• Drag-n-drop arrows/relationships between Tasks/Boxes to setup Task dependencies. Display dependencies diagramatically #2921

... and if it does not do roughly what you are wanting, then we would need more info in this ticket to keep it open.

[blueeaglex]

@claremacrae Thanks！ The topic you referred was close to my idea but not exactly what I propose.
I can use a use case to describe it:
In 01 June, I launched a project.
So I record it in my diary of 01 June as a super task named A like this:

01 June 2024

• A 🆔 0
  • sub1
  • sub2

Maybe I could know that to accomplish A I need to do 'sub1' and 'sub2'.
But I'm not sure if that's all sub tasks before I got any progress.
So I add more sub tasks to project A in the incoming days in other diary files, for example:

05 June 2024

We have big progress but the job isn't done yet, we need to do more work:

• sub3 super project 0
• sub4 super project 0

Does the plugin support the use case for now ?

[claremacrae]

I've converted this to a Q&A, as it isn't a feature request... It's about how to use the existing facilities, when spreading details of a project across disconnect daily note files.

I will reply to it when I have time.

[blueeaglex]

I've found a way to do reach the goal similar with the use case mentioned above.
I wrote some tasks in file A like this:

title 1

• Task a 🛫 2024-07-19 📅 2024-07-20
• Task b ⏳ 2024-07-19
• Task c ➕ 2024-07-19

title 2

• Task d 🛫 2024-07-23
• Task e ⏳ 2024-07-23

And in file B:

title 1

• task f

Then in my task view file:

```tasks
path includes test
group by heading

Then I made it ! I can define sub tasks in different files for the 'super task' of 'title 1':

But I don't think it the best practice because I was just making my self believe that 'title 1' is a super task.
Are there any better solutions?
@claremacrae

[blueeaglex]

Hello @claremacrae

[claremacrae]

Apologies for the slow reply, in part because I am not really sure that I understand what the question is here.

I wonder whether the problem you are having is because of storing tasks in files or headings that are named after the dates the tasks were created, rather than structuring them based on the structure of information that they are about.

I have a file for each individual project, and as that file grows, I use a plugin like Note Refactor to divide it up at the section headings in to different files.

Then my searches can be simple things like:

## Tasks in This File

```tasks
not done
path includes {{query.file.path}}
```

Or

## Tasks in This Folder

```tasks
not done
folder includes {{query.file.folder}}
# group by folder
group by filename
```

I have Templater templates for those two searches, as I use them in many places in my vault, for quick access to things I need to do around individual topics.

[blueeaglex]

I wonder whether the problem you are having is because of storing tasks in files or headings that are named after the dates the tasks
were created, rather than structuring them based on the structure of information that they are about.

Yes, you got it. Apologies for the confused information and thanks for your alternative solution.

I have a file for each individual project, and as that file grows, I use a plugin like Note Refactor to divide it up at the section headings into different files.

I think this must be better than may diary list.

LOL.
As days grow. I found it really sucks. The title named by date has no sense at all and has no help for search neither. I think it's time to change that! Thanks again.