How does the task assignment feature work?

How does the task assignment feature work?

Flowsana's Dynamic Duration-Based workflow has the ability to automatically assign tasks when they become available to be worked on. This feature is designed to solve the Asana limitation whereby if you assign a task to someone in a template, that task appears in the assignee's My Tasks list, which is not expected or desired since the task is only a "placeholder" in a template, not an actual concrete task to be worked on.

So how does Flowsana's task assignment work?

Task assignment only occurs when a task is a dependent task and its predecessor task gets marked complete; or if it's not a dependent task, when you first enter an overall project start date.

So for example, say you have the following scenario, and say that "Write press release" is dependent on "Determine product or feature name", and that "Press outreach for launch" is dependent on "Write press release".



What will happen is the following:
  • When you initially enter an overall project start date, "Write positioning and messaging brief" will get assigned to Jane Smith, and "Determine product or feature name" will get assigned to Phil Seeman. WHY? Because, since those tasks are not dependent on any other tasks, that means they can be started right away, so they are assigned right away. The other two tasks (in the PR section) can't be started yet since they are dependent, so they are not yet assigned.

  • When you mark "Determine product or feature name" complete, "Write press release" will get assigned to John Wilcox. WHY? Because now that its predecessor task is complete, work on "Write press release" can begin, so it is assigned.

  • When you mark "Write press release" complete, "Press outreach for launch" will get assigned to Jane Smith. WHY? Because now that its predecessor task is complete, work on "Press outreach for launch" can begin, so it is assigned.
Also please note that for the assignments to occur, the name you type into the Assign To column must exactly match the name of the user as it exists in Asana.

    • Related Articles

    • How Dynamic Duration-Based Workflows Work

      CUSTOM FIELDS When you put a project under control of a Dynamic Duration-Based workflow, it attaches three custom fields to the project. (If any of these fields doesn't exist, Flowsana creates it.) Duration : This is a number of days, weeks, or ...
    • Creating Unique Task Short IDs and Short Links

      Using Flowsana's If-Then Rules and Variable Substitution capability, you can create unique short IDs and unique short URL links for your Asana tasks.  Short Id - creates a short numeric ID that is unique within the task's workspace/organization. ...
    • How can I keep a task synchronized to the same column in two projects?

      Because sections are specific to projects and are not shared between projects, you can’t accomplish this directly. So what you can do is use a custom field (you can also use a tag) to in essence link the two projects together, and then create rules ...
    • How does Flowsana's pricing work?

      Flowsana's pricing works based on the concept of Billable Users. A Billable User is an Asana user who's a member of a team having workflow-enabled projects. Flowsana charges at $2.99/month USD per Billable User. Say you have a Marketing team which ...
    • When I specified a Duration of two weeks ("2w"), Flowsana created a task length of 20 days, not 14 days

      That's correct.  As specified in the documentation, Flowsana calculates in terms of working days, and it skips and ignores weekends.  So it interprets "2 weeks" as 14 working days.