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 ?