◆ Asana

Migrate and bulk update tasks

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 taskMove all tasks from the 'Old CRM Migration' project into the 'New System Implementation'…+
Move all tasks from the 'Old CRM Migration' project into the 'New System Implementation' project, keeping their original due dates and assignees.
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 the end of the quarter, take all overdue tasks from the 'Q2 Marketing Initiatives'…+
Before the end of the quarter, take all overdue tasks from the 'Q2 Marketing Initiatives' project that are assigned to John, and reassign them to Maria. Also, update their due dates to two weeks from today. I need to clear John's plate and get these moving again.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentLeadership just announced a complete reprioritization of the product roadmap, meaning hundreds…+
The product roadmap just got completely reprioritized by leadership, meaning hundreds of tasks across multiple projects need new due dates and assignees, and I'm overwhelmed.
Leadership just announced a complete reprioritization of the product roadmap, meaning hundreds of tasks across the 'Feature Development', 'Bug Fixes', and 'Discovery' projects now have incorrect due dates and assignees. My team is already asking for clarity, and I'm afraid of the chaos if I try to update them one by one. How can I quickly bulk update all tasks with the 'High Priority' tag to new due dates and reassign them to the new leads without losing critical context?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly losing time and credibility whenever there's a major shift in project scope or…+
Every time there's a major shift in project scope or team structure, I spend days manually updating tasks, leading to delays and frustration.
I'm constantly losing time and credibility whenever there's a major shift in project scope or team structure, because I have to manually update hundreds of tasks. It's a huge drain and delays getting the team back on track. What's the best habit to change so I can efficiently handle large-scale task migrations, reassignments, or due date changes across multiple projects without getting bogged down in manual updates?
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.