I would request that you would add or allow us to create rules based on subtasks.
For example in a project flow - I have a task that contains multiple sub-tasks. This task is connected to my editorial calendar and the due date on the task is based on when it will post, but I would like to create rules for my subtasks. So as I change the status of the task it can automatically change the due dates on the sub-tasks. Right now I have to manually do this and it is quite time-consuming.
I could create tasks that are larger but having one task house my sub-tasks is a much more organized method.
Absolutely, thatâs a great idea! I think rules across the board for subtasks would be helpful. Even for example, marking a subtask complete should be able to trigger moving that task to the another column and updating the master task status.
I couldnât agree more. Now that the first layer of subtasks are visible from the project pane AND Custom Fields are carried over to them, it would be really efficient if they could also be a trigger in Rules. The primary area where I would find this extremely valuable is for multi-homing purposes. I often find that I need to see subtask data across various projects in a consolidated view. This automation feature would completely eliminate that extra step to ensure that ânext needâ is configured!
Agreed. I just ran into this issue myself. I have created a project as a checklist for my guys to check for bugs in our companies custom software. It is full of over 1400 subtasks for each of them to check and make sure features are working correctly. The main tasks are not actually tasks, but group labels, which are further nested under sections, that I also must use to label the higher level group.
As soon as they find an issue in our software, I want them to assign the task (with their comments on the issue) to our developer. As soon as they would assign this subtask (the actual task) to the developer, it should add this task to another common project that all of the guys see. This way everyone can see what kind of issues the other guys are submitting, without having to have access to their projects and looking through them.
As long as rules donât apply to subtasks and the workload feature doesnât include subtasks either we wonât be upgrading to asana business as those are pretty much THE key features.
As is, that plan is super unattractive to anyone relying on subtasks a lot.
We would like to work non-linear with our tasks/subtasks. When a subtask is marked as complete the task moves then to another column and / or in another project. The task is then visible in two projects when the subtask is marked as complete.
A project is part of the process for us.
Project 1 is Operations
Project 2 is Processing
With us, a task goes from project 1 to project 2. But when a certain subtask in project 1 has been completed, it should already be visible in project 2.
Now a subtask can be linked to another project, but then it is also immediately visible in that project, but would like it to be visible when marked as complete
Just wanted to add our use case for how this would be helpful! I would love for a status update on a task to automatically create a subtask within it and assign to a person on our team. For example, in our project where we are managing all of our articles, when the task status is âInternal Reviewâ it would be fantastic for that to trigger the creation of a subtask of âReview this articleâ and assign to our Content manager.
Adding on, we donât want to just change who the task is assigned to so that we can keep up with who on the team is more directly managing each piece.
I use forms and have Asana set the custom fields and add comments through rules. Itâd be great if the RUles could also add subtasks to the new task the form creates.
You might be interested in the âAdd subtasks from a templateâ rule action of my Flowsana integration. One common use of it is exactly what you mention - to add a specific set of subtasks based on data within the form submitted.
Hi @Agnes_Eaker, we already have a #productfeedback thread on this topic, so Iâve gone ahead and merged your post with this main topic to gather all comments and feedback in one place! Iâll keep you posted when I have an update on this topic!
The ability to add subtasks via a rule would often be used.
Use Case:
When a task is added to this project, add subtasks âPublish On Socialâ
When a task is added to this project, add subtasks âQA Scope Requestâ
When a task is added to this project, add approval subtasks âApprove Change Requestâ
When a task is added to this project, add approval subtasks âApprove Purchaseâ
Not rushing, I just want to know if there is any update from Asana on this?. Because I just have read a lot of old Asana posts related to this regard. And apparently, this feature doesnât appear as officially on Asana plans yet. And the best solution is the integration with Flowsana (that I found not much intuitive and easy-going).
This Topic needs a certain number of votes so Asana Development Team considers implementing it?.
I donât have an update on this topic yet, but I will post an update here as soon as I do! Our team is aware this is a popular request, but before we can implement Rules for subtasks, we need to perform some essential upgrade on subtasks. While I donât have a clear timeline to share at the moment, rest ensured this is something our team works on priorising. Iâll keep you posted here as soon as I know more!
In addition to this, (perhaps already purposed in another thread) It would also be great if (some) rules could be implemented for the entire Workspace or team?
e.g. If task is set to Assignee X - Add task to board X?
