You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The hierarchical relationship between parent tasks and child tasks is identified abnormally; tasks that do not belong to tasks with the #ticktick tag are marked as child tasks.
To Reproduce
Steps to reproduce the behavior:
The current task tree structure is as follows:
test1
test2
test2.1
test2.2
test2.2.1
test2.2.1.1
test2.2.2
test2.3
test3
Now, add the #ticktick tag to the task test2.2.1, and it will be synchronized to ticktick.
test1
test2
test2.1
test2.2
test2.2.1 link #ticktick %%[ticktick_id:: 678fc21a1b9ca0c50e2e5908]%%
test2.2.1.1
test2.2.2
test2.3
test3
After triggering the synchronization logic, the task tree structure has become as shown in the figure.
Expected behavior
Should only test2.2.1.1 be recognized as a subtask
The text was updated successfully, but these errors were encountered:
Additionally, there is a strange phenomenon where when I focus my mouse on a specific task and then move it away, that task gets added as a subtask and is marked with an ID.
Actually, test2.2.1.1 should be a task item because it doesn't have #ticktick tag and is indented.
but yes, everything below that should NOT be task items.
Additionally, there is a strange phenomenon where when I focus my mouse on a specific task and then move it away, that task gets added as a subtask and is marked with an ID.
That's weird! The plugin doesn't do anything on onhover.
Will try to reproduce. In the meantime: What plugins do you have installed?
Describe the bug
The hierarchical relationship between parent tasks and child tasks is identified abnormally; tasks that do not belong to tasks with the #ticktick tag are marked as child tasks.
To Reproduce
Steps to reproduce the behavior:
The current task tree structure is as follows:
Now, add the #ticktick tag to the task test2.2.1, and it will be synchronized to ticktick.
After triggering the synchronization logic, the task tree structure has become as shown in the figure.
Expected behavior
Should only test2.2.1.1 be recognized as a subtask
The text was updated successfully, but these errors were encountered: