◆ Asana

Edit multiple tasks in bulk

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskIn the 'Website Redesign' project, change the due date for all tasks currently assigned to…+
In the 'Website Redesign' project, change the due date for all tasks currently assigned to 'Laura' from 'Friday' to 'next Monday', and update their status to 'In Progress'.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore our next sprint planning, go through all tasks in the 'Development Backlog' project that…+
Before our next sprint planning, go through all tasks in the 'Development Backlog' project that are currently marked 'Low Priority' and have no assignee. Assign all of them to 'Unassigned Backlog' and add a tag 'Review for Q3'.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe client just decided to pivot on the main feature for the 'Mobile App Development' project,…+
Our client just changed their mind on a key deliverable, impacting twenty related tasks across two projects.
The client just decided to pivot on the main feature for the 'Mobile App Development' project, which means about twenty tasks across that project and the 'QA Testing' project need their descriptions updated, due dates pushed, and a new 'Client Pivot' tag added. I'm worried I'll miss one or introduce inconsistencies. What's the best way to make these changes quickly and accurately without breaking anything?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWhen project requirements or deadlines shift, I spend an excessive amount of time manually…+
I waste too much time manually updating individual tasks when project requirements shift.
When project requirements or deadlines shift, I spend an excessive amount of time manually opening and updating individual tasks, changing assignees, or adjusting dates. It's tedious and prone to errors. What habit should I change to manage these bulk changes more efficiently and reliably when the inevitable project pivots happen?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Asana's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.