I’m in an Asana trial period. I’ve created a rule using Asana AI Studio that does the following:
When multi-homing a task (add the task to another project), check for the matching section and move the task to the matching section. The rule runs appropriately, but I’d like to “look under the hood” to see how it was built and be able to build the rule myself. I can’t locate documentation on whether Asana’s AI Studio has a view that shows every step it took.
The first screenshot shows the rule I created using AI Studio, and it works appropriately.
The second screenshot shows the rule I’m trying to create without using AI Studio. I started to test using only 2 matching section names to start with, and it hasn’t run successfully (“rule hasn’t run yet” displays in top right corner, even after I’ve tested multi-homing a task in the 2026 Project Summary). I’m unsure if this approach will work.
1 Like
Hi @A_Claudio and welcome on the Asana forum 
There is no way to view the internal logic of an AI Studio rule, Asana does not expose a “step-by-step” view of what AI Studio built under the hood.
That said, you can try to recreate this manually with the standard rule builder.
BUT this condition doesn’t exist natively “which section the task was in the original project”.
Indeed, sections only belong to the project where they exist, and can’t be “called” from another project (at least not without a smart feature like AI Studio).
A workaround could be:
- Create a field in the original project to represent the sections (in parallel, or instead of sections).
- Add that field to the library
- Add that field to your new project (from the library)
- Use that field as an identifier for your rule (same as your screenshot 2, but conditions will be based on field, and not section)
More info on using fields as sections:
Hope that helps.
Feel free to ask more questions or identify my answer as a solution
Arthur
Arthur: Thank you for identifying possible solutions and clarifying that AI Studio doesn’t allow for “looking under the hood.”
Adding fields as sections seemed a bit clunky, but I just realized that using Workflow view (which is available in the Starter plan, which is the plan we would start with if adopting Asana) might help, and it worked! It replicated what AI Studio had done. It easily walks through creating the rules.
When tasks are added to this section > Add to additional project > choose a column/section
See screenshots:
1 Like
Well done Claudio, that’s definitely another way to do it.
