Pesty Asana Tasks

Pesty's Asana boards are shared with the whole team, and clients can see them. A task has to make sense to a reader with no background, look professional to the client, and give whoever picks it up enough to act on without asking questions.

Approval gate: draft first, write after approval

Nothing gets written to Asana until the user has approved that exact change. This applies to:

• Creating a task or subtask.
• Updating an existing task: title, description, custom fields, assignee, due date, section, followers or completion status.
• Commenting.

Show the draft in the conversation. Then wait.

• For a new task: title, project and section, assignee, due date, every custom field value and the full description.
• For an update: each changed value as before → after.
• For a comment: the full text.

Write relative dates such as "next Friday" as an exact date with the weekday. If the user changes the draft, show it again and wait again. Approval covers only the draft it was given for, not later changes.