Aisys Task Template Sync
Setting up your pipeline
Aisys works out which columns to update from their names. Get the names right once, and every update after that just works.
- Task template
The task you duplicate each time a new job starts. It usually sits in a column of its own.
- Live task
A copy of the template, moving through the pipeline.
- Template section
A heading inside the template's list of subtasks. Asana calls these sections.
Which columns are updated
- 1A column named exactly like one of your template sections is updated. These are your pipeline's stages. If a name is nearly right, the column is still updated, and your report asks you to make the two names match.
- 2A column whose name starts with END: is where finished jobs go. For example, END: Lost Instruction. Its open tasks are still updated, in case a job comes back. The colon matters.
- 3Every other column is left alone. Templates, reference, admin, anything else you keep on the board. Your report lists these columns, so you can rename one if it should be updated.
Your report shows every column
Each report starts with your columns side by side with your template sections, and lists anything to fix. Fix it in Asana, refresh the report, and the fresh one shows the change.
Looking after your task template
- Tag the template, not a live task. A subtask can't be updated on its own: tag the template and every subtask comes with it.
- Making a new version of a template? Duplicate the old one and change the copy. Its first report shows it taking over the old one's live tasks.
- Complete or archive an old template, never delete it. Aisys traces each live task back through the template it was copied from. Delete the old template, or a subtask in it, and those live tasks can't be traced any more.
Finished live tasks are never updated. Mark a job complete and it keeps the version of the process it was done with.