Parent Task Dependency Still Allows Completion

Briefly describe (1-2 sentences) the Bug you’re experiencing:
When I set the parent task dependent on another task, I am still allowed to complete the parent. This does not happen with subtasks dependent on other tasks. You cannot complete a subtask that has a dependency, this should apply to parent tasks as well.

Steps to reproduce:
Set the parent task dependent on another task.

Browser version:
Upload screenshots below:

1 Like

Hi @Getz_Pro and thanks for reaching out! This is currently an expected behaviour, if you haven’t yet, you can addd your vote to the following #productfeedback thread: Task Dependencies - the missing piece. Hope this helps, but let me know if you have any follow-up questions :slight_smile:

Hi Marie,

Expected behavior is to not have it behave as it does elsewhere? Who expects that? No one lol


Hey @Getz_Pro,

It’s actually not a question of parent task vs. subtask - they work consistently with each other in terms of completing. Rather, it’s a question of where you’re doing the completion-marking.

You can no longer mark a dependent task complete from the list view, but you can do it via the “Mark Complete” button in the task detail pane. (“List view” meaning both the main project task list view and also the task list view of subtasks within a parent task.) The reasoning is that apparently people are marking tasks complete in the list view without really realizing they are dependent on something else; forcing the user to go to the task detail pane to mark it complete causes them to see the dependencies there and be more conscious of marking it complete.


@Phil_Seeman you are suggesting that Asana breaks depending on where you use it? Really? When you get everyone use to the flow of dependancies and then that workflow breaks depending on where you use it, it is really hard to get people aligned.

Just sloppy, call it as it is.

Well, I assert that “breaks” is the wrong expression here - “breaks” connotes “doesn’t work the way it was designed and coded”, whereas the current behavior is absolutely the way it was designed and coded.

Now if you were to say, “you are suggesting that Asana works inconsistently depending on where you use it such that it confuses my users and makes it hard to get them aligned?”, then I’d say, “Yes, it does, and I agree 100% that inconsistency shouldn’t be there!”

1 Like

@Phil_Seeman asana has bad design in its code, thus it breaks according to how it is used in one aspect over the other. Designing a flaw doesn’t make it a feature. Do you work for Microsoft as that is their mantra.