Non-form submissions as a rule option

English Forum Product Feedback
, ,
1

When adding a rule to the project, currently I only have the option to select:

  • All tasks ; or
  • Form Submissions

What I would like is to have another option:

  • non-form submissions

Here is why:
Our business is not all in Asana. The form is the main source of intake. But for those who already work within the platform, they can add new tasks to the project directly. I would like to create a certain routing with some rules only to those created within the project.

Screenshot 2024-12-05 at 10.25.27
Screenshot 2024-12-05 at 10.25.27474×259 9.25 KB

2

Hi @Rashad_Issa , I would definitely find this useful (I voted) but until/if it becomes available, could you perhaps have a dedicated section for adding such tasks? That section could be the condition to your rule.

3

Thanks @Richard_Sather

Wouldnt this new section and rule clash with the one that exists for when new tasks are added to the project?

I now have a rule that when a task is added to this project, it comes to New Request and is marked approval. The rule is done on ‘all tasks’.

4

Is that rule in place simply to add all form intake tasks to the New requests section? If so, you don’t need this rule anymore because you can now set the ‘landing’ section within the form’s settings.

5

@Richard_Sather Yes, that is a brilliant setting with forms.
the rule is not about the routing of the task.
It includes marking tasks as approvals and using few custom fields that are used from the form submission to trigger some actions.
If someone is adding a task directly from the project, then these fields are empty, and I want to create a different set of criteria around emails and notifications.

6

Hey @Rashad_Issa,

FYI this is available in our Flowsana integration rule triggers:

image
image435×189 4.2 KB

2 Likes
7

Ok so perhaps you could have one rule act on tasks added to a particular section where tasks are added into from your form. And then have another rule which acts on tasks manually added in another specific section.

You could optionally have a 3rd rule without a section condition that would act on all tasks added to the project, regardless of form or not, such as marking a task as an approval.

1 Like
8

Thanks Richard. I will play with this and see how I get on. Much appreciated.

1 Like
9

I’m a little late to the game, but if you’re not using Flowsana and until Asana adds this, I’ve worked around it by using a rule that targets form submissions only to set a single-select custom field “From form?” to :white_check_mark: so that you can have other rules ask if “From form?” is unset, then that’s how you know it wasn’t added by form.

Thanks,

Larry

1 Like
10

I have a project that compiles form data and manipulates it in the task description to create a work order that is printed for non-Asana users. We are able to create a specific format using the ‘Task is added to this project by “Form submissions”’ trigger and “Set task description to” action.

I would like to be able to trigger a different template to be filled out for tasks that are added manually. The problem is if I select “All tasks” this also adds the new format to end of the description of the form submissions. I know that I could create task templates, but some of the manual submissions will be added by seasonal staff and I’d like to keep it as simple as possible.

What I would like to see is the addition of a ‘When Task is added to this project by “Manual submissions”’ trigger. This way I could have a rule create the proper format when the user simply clicks anywhere in the project to create a task.

11

Hi @Jeremy_Long , this sounds quite similar to this recent post by @Rashad_Issa which you may consider merging into
?

See the post by @lpb and my suggestion, too.

1 Like
12

You beat me to it, @Richard_Sather! I agree both that these workarounds may help and that merging sounds good to me too.

Thanks,

Larry

1 Like
13

I missed that one @Richard_Sather, thank you!

2 Likes