Does anyone have any workaround for automations only being applied to a single task type per automation (or for setting the billing type)?
We have about 20 custom item types per space and are running 5 spaces. Each space represents an individual client. 99.9% of tasks need to be billable in each space.
Tasks are created either by request form or directly into a kanban view of our workflow.
(The kanban view lives in the space overview).
In order to ensure that we are able to set the billing type of each task to billable, we must move each task from the space overview and into a project that has the billing type set to billable ... this took me a while to figure out!! I can tell people to use the billable project to create tasks in, but they don't always remember!
The problem doesn't end there. Moving tasks does not make them billable because they are not created within the billable project. If a task is created by a request form, we can move the task or item type into the billable project using the automations available within the request (this is great, thank you!) ... However, the job, of course, does not end up as billable.
The only in order to catch everything we need to create an automation.
But the problem here is two-fold.
- Automations only work on one single task type at a time....do I really need to create 20 automations to do the single task?
- There is no automation to change the billing type.
If anyone has any workarounds here I would really appreciate hearing them.
Thanks.
Hello Benjamin Rodd, thank you for sharing your question with us. In this case, you'd need to either create an automation rule for each custom item type or, create a rule that would apply to all the tasks gathered in one specific location. I believe this would be the easiest way.
In case you still wish to request users to make the changes manually, you can create a rule to @mention the item's author and ask them to make sure they are using the billable project.
Please, let us know if you have any additional questions!