Setting Dependent Task Dates Based x Days From Completed Task

English Forum Product Feedback
1

It would be brilliant to be able to set a task or subtask due date based off of another task being completed.

When setting the Due Date for a task that is a dependent of another, we can set the due date x days from the completed task.

5 Likes
2

There is a way to do this by integrating an additional software to connect with Asana.

3

Are you referring to Flowsana?

1 Like
4

Not sure if she was referring to it or not, but Flowsana does provide this capability using the Lag Time feature of its Dynamic Dependency workflow type.

3 Likes
5

Not at all interested in 3rd party add-ons, but for Asana to add it and support it. But thanks.

5 Likes
6

Yes sir! Have you tried it?

7

I did, I don’t have a use case for it anymore, but Flowsana from @Phil_Seeman is a big reference in the Asana ecosystem.

8

I completely agree with you.
Shouldn’t be a big deal for the developers to program this feature.

9

If they did everything that was simple, the app would be a Christmas tree of buttons and fields :slight_smile: :christmas_tree:

11

Please add in this feature! Pretty crucial to scaling timelines & processes.

12

Love this idea - not sure if this is the same idea or a different topic altogether, but would also be great to add this relative timing into project templates.

13

This feature gets my vote as well. I think it is good to expand the great capability of templates to set up dependencies based on dates.
Considering I use a lot of use of asana for marketing campaigns, I am surprised that this feature is not voted in a lot more.

14

Like appreciations? :roll_eyes:

15

You aimed for the heart :heart: :sweat_smile: can we vote for a feature to disappear and be replaced by another? :grimacing:

1 Like
16

I am sort of astonished that this is not an option.

I thought the use of rules and the ‘Task is no longer Blocked’ trigger would do the trick, as I could then set a due date in the Rule. However, I now see that the rule triggers every time ‘any’ task is no longer blocked, which makes it useless when we are trying to be granular to the task level.

Hopefully, I’m missing something :roll_eyes:

17

Rules are currently all about about “any” task matching the criteria. You can’t have rules targeting a specific task. Zapier & co, with their filters for example, will be able to help.

18

I completed agree that this small feature can save 1000’s of hours globally.