Shouting out to the Asana community to see if anyone has experience or a resolution to a reporting block.
I am part of a team running 2-week sprint periods, completing a number of tasks and needing to report on team achievement during that sprint period. I have a number of custom fields setup to track pieces of task attribution, such as:
- Priority
- Task type
- Assignee
- Sprint points (task size)
I have been experimenting extensively with both prompts within Asana AI, and manual/date and time triggered rules within AI Studio. The overview of the prompt breaks down to requesting alphabetised bullet lists for the above points, counting the number of times each value from the custom fields is used on tasks in a specific section of my project.
In Asana AI, the experience is an incomplete set of results, iterating by telling the model where it has made mistakes, it apologising and doing slightly better, before it finally arrives at the correct set of results after 5-8 iterations. This takes long enough that it is faster doing it manually.
In AI Studio, the rules all fail, for a number of reasons:
- Unable to create a comprehensive sprint report because I don’t have access to all tasks in the ‘Completed Tasks’ section
- Can only view tasks surfaced by a search, not as part of a whole project section
- I’m unable to complete this sprint report because I don’t have the ability to run an advanced search to retrieve all tasks and subtasks from the ‘Completed Tasks’ section
- I need you to @mention the project section you want to pull tasks from (as far as I can see, you can’t @mention project sections)
Has anyone out there been successful in automating the creation of reports on segments of project tasks please? All advice and suggestions gratefully received!
Hi @Adam_Bennett
Totally get the pain here. The most stable fix is to switch from sections → fields or a helper structure so reporting becomes deterministic.
Option 1: Use a Sprint custom field (best long-term)
- Create a dropdown field: Sprint (e.g., Sprint 14, Sprint 15)
- Add a rule: when task is completed → set Sprint = current sprint
- (Optional) apply same field to subtasks via rules or structure
Then you can report cleanly by Sprint instead of sections.
Option 2: Use a helper project per sprint
- Rule: when task moves to Completed Tasks → also add to project “Sprint 15 Completed”
- Now reporting is based on a clean, dedicated dataset
This avoids section limitations entirely.
Build reporting from there
Use either:
Advanced Search (Completed + Sprint = X / date range), or Dashboard charts
Then group by:
- Priority
- Task type
- Assignee
- Sum of Sprint points
On the AI side, you’re right. AI Studio and Asana AI can’t reliably @mention or scope sections, and they may miss or inconsistently interpret tasks. They work much better when you feed them a stable dataset like a saved search or helper project, and then ask them to summarize that fixed set rather than trying to discover tasks dynamically.
Overall, the key shift is moving reporting logic out of AI and sections and into custom fields, helper projects, and dashboards, which is what makes sprint reporting scalable and consistent.
Some great points there - thank you @Iren_Vilaniso! I’ll give them a go and let you know about the successes or potentially other questions which surface through this shift.
@Adam_Bennett I’d be happy to dedicate some time to this issue if you need help. Just send me a message. I’ve worked with sprints in Asana before and enjoy that puzzle. @Iren_Vilaniso has already put you on the right path with custom fields.