Hi,
I have set up rules for a project for when a task is added by form with select specifics to add those specifics to the task as a subtask. It will then take the task and convert the task to a project. The project then is sent to a portfolio based on the specifics. However, the rules run at random, and while in the middle of adding the subtasks, the task will convert to a project, leaving out more than half of the information. I need help with having a set of rules run first and apply to the task before it is converted to a project. The problem resolved itself about a month ago, and my rules ran perfectly and fast for about two and a half weeks. None of my columns changed and no new information was added. I have read that changing the order of the columns may change the order that the rules are run, but this did not help. I have contacted Asana for support, but it took them three weeks to respond to me, and I am assuming that it will take them longer to fix the problem and respond to me. This is the only problem holding my team back from using Asana full time. Does anyone have any suggestions? I would appreciate the help.
Thanks!
@Ajkosmo34 - have you set this all up in one rule (with multiple branches and actions for each branch) or as a series of rules? If it’s the latter, you could either try to do it all in one rule (so it runs in logical sequence) or use a custom select field with option(s) representing the different rules, changing that field to the correct “status” after each rule run and using that as a condition for the next rule.
1 Like
Hi @Stephen_Li ,
I have it set up as several rules. I have tried setting this up as one rule, and I have not been able to find a way to format it so that one or all of my options appear in the task when selected on the form. I am using the Multi-Select field for my options. When one is selected on the form, then it should make the one subtask appear under the task. Same thing if multiple were selected, then multiple subtasks will show up under the task, what ever the order may be. If there were an option to set the subtask rules to run and then run the project conversion rule, then all may be well. I appreciate the suggestion, but if I had to change the field each time for each project that came through from each person on my team, then this program would be pointless.
@Stephen_Li
I think I see what you are saying about having a custom category after each rule. However, that would be seven more rules to be added in to the 22 that I have set up.
@Ajkosmo34 - each branch of a rule can have multiple actions, so you would either include an action to set the status field or just convert to a project in the same branch (or are you saying that the rule actions within the same rule branch are not happening in sequence, as opposed to individual rules firing in random order, which is expected behavior I believe)?