While we mostly use just subtasks for this purpose, sometimes it would still make sense to be used if required pre-task is from other area.
Sadly UI/UX and naming of these are so weird that even with guide I have 0 idea which one is which. So even if I would understand it, my team will not, as I have enough of troubles ensuring they use other simpler things correctly.
"Predecessor and Successor" are too complicated words by itself at first. I never saw any other task management software using so hard (for non-EN native speakers) words.
Secondly, this is unclear which one I should define if I want for example #6420 task to be done before this? Is this Predecessor? Even if you would explain it to me, I will forget again. This needs better visual such as emojis with arrows or showing visual tree.
Lastly, guide itself could explain it more (which is which) especially for people who never used such feature.
Plus this different naming in guide is misleading:
Plus imo you should add confirmation box if you want to complete task while previous task is not completed, as many people is not reading descriptions and won't notice "depedencies" at all.
Hi,
Thank you for sharing your feedback about task dependencies. We've passed it along to our team for future improvements.
We're also planning to update our guide to make task dependencies easier to understand for all users.
You’re right about the need for a confirmation dialog when completing a task that has dependent tasks. Our team recognizes the importance of this and is looking into it. While we don't have a timeline yet, we'll be sure to keep you updated if there are any changes. Stay tuned!
Golda, May 14, 2025