Customize your progressions to set a touch-point schedule for a sale or a support ticket, such as to follow-up with a lead every 2 weeks, or to update the client on your service ticket every 72 hours by adding a Create Task action to your status change.
Using this guide, you can:
Define one or more tasks that a user will be prompted to review and create during a progression with the Create Task action. This is very handy for managing recurring work and support issues.
Note: The Create Task action is not available on Projects because a Task created in a Progression can greatly increase the risk of user-error in with budgets and billable work. For your Projects, we recommend building in a Special Process to go to the Plan instead if you wish to add a Task. This will ensure the user knows they are adding work to a Project Plan.
To create a Create a Task action:
Find the progression you want to add an action to, click the + button on the right-hand side, and select Create Task.
The Create Progression Action Field screen will appear.
You can then configure the default values for the task, such as:
Title - This will be the name of the Task.
Manager - Select the default manager of this task.
Start and Due - These are the dates that the Task should be started on and completed by. These dates can also be defaulted based on the current day, but you can set them to any future date.
Estimated Time - The number of hours and minutes estimated to complete the Task.
Notify - Whether, by default, the assignee will be notified by email that a task has been created for them.
Required - Whether or not the task must be created to complete the progression.
Hidden - To allow the user running the progression to see and modify the details of this task, select No. Otherwise, choose Yes and have the task automatically created in the background during the progression.
Whenever a Task is created through these actions, you can always include pre-defined fields inside your template.
For example, you can always set it so your body always includes the Budget, Title, and ID of the object in your automated Task utilizing the merge fields.
A popular one is to start the body with [issue.deadline] to notify the assignee of when it’s due in the body. This will alert them of the Due Date in the notification, without reading directly into the Task itself.
Merge field options vary from module to module, but they’re always presented on the Task template.