We've noticed that when configuring request forms with blueprints that consists of tasks + subtasks, that our internal team uses to fulfill the requests, the person that submits the request automatically is granted access to all those tasks that are created automatically, which isn't desirable, specially if the person is a customer (external collaborator)
To avoid this, one potential solution would be this:
- Request form is filled and a task A is created with description + custom fields filled with the responses.
- The new task is created in folder X and will serve as a way for the requester (external collaborators) to see that their request has been received.
- Upon creation, a 1st. automation action would take this task and duplicate it as task B on a separate folder Y, where our internal team works on the requests. This has the benefit of retaining all the task details.
- This would also trigger a 2nd action where subtasks will be created inside task B.
- This would result in the following: Folder X > Task A (for the customer) & Folder Y > Task B > Task B1,Task B2, Task B3, etc. (for our internal team)
This way, the customer isn't automatically granted access to see all the subtasks our internal team uses to fulfill the requests.
The current actions in automation can only duplicate existing tasks or blueprints, but I believe there isn't an action available to duplicate recently created tasks dynamically which is needed in step 3 in the above potential solution.
Are there any plans for this type of dynamic actions? Or any workaround for our use case?
Thanks for any help in advance.