Hi @K_Taylor,
As @Bastien_Siebman mentioned, Flowsana has a rule action that adds one or more subtasks from a template. So in your case, you could have a rule like âIf a task is moved to the âNext Phaseâ section, add these subtasks to it.â
Hi @K_Taylor,
As @Bastien_Siebman mentioned, Flowsana has a rule action that adds one or more subtasks from a template. So in your case, you could have a rule like âIf a task is moved to the âNext Phaseâ section, add these subtasks to it.â
I recently asked if there was a way to get workload on product roadmaps and found a work around to get this to happen, but would love to create a rule for my workaround.
In my product roadmap all sub tasks to the roadmap items are the actual tasks to complete them. Iâd love to create a rule that anytime a sub-task is added to my roadmap project, itâs automatically added to another project (which Iâm using as an input to my portfolio for showing team workload). I can create rules for tasks being added, but not sub-tasks.
Thanks,
Kelley
Subtasks are limited currently throughout Asana.
You can multi-home a task with another project and in doing so, that task will be a parent in that project. Then you can trigger a rule as normal and add to a portfolio for workload.
Subs can be access in Universal Reporting, so this leads me to believe a future state will include them in other areas over time.
Hi @anon13627270, thanks for sharing your feedback with us! We already have a thread on this topic so Iâve gone ahead and merge this post with the main thread to consolidate feedback.
Hi - I understand that subtasks arenât part of a project so rules from a task donât apply to them, howeverâŠ
We use rules in this way.
For onboarding new customers, we create a dedicated project. The project contains tasks, and then we break down the tasks into parts as subtasks under the task.
We have rules that when a customer creates a new task or adds a comment on a task it adds that task into a completely separate project called âUnanswered Questionsâ. This way, our support and onboarding team has a quick place to see ALL tasks that have been updated or added as opposed to having to go into every single project separately. When they are done answering the question or updating info, they remove it from the âUnanswered Questionsâ project.
This breaks down when a customer adds a subtask or comments on a subtask. Weâd also like these to be automatically added to the âUnanswered Questionsâ project.
Is there a way to do this?
Hi,
Because subtasks are not part of the project (you said it right), Rules âon a projectâ canât apply to them. Otherwise Asana will have to contradict themselves and create specific code. Your only chance is that subtasks are added to a project (or THE project) as well as being a subtask. But I always advise against this kind of solution because it is hard to understand, and you usually forget to multi-home the subtasksâŠ
If the client is allowed to create subtasks, he will never think about multi-homing themâŠ
Have you considered using Sections + Tasks instead to break up your project, instead of Tasks + Subtasks? That would allow you to keep the same workflow and to fully leverage Rules!
We already use sectionsâŠ
Weâre in e-commerce software, so as an exampleâŠ
AndâŠ
I understand that subtasks are NOT part of the project, but I canât say I understand WHY Asana made this decision. Jira and numerous other platforms have subtasks and they are all part of the project the task belongs to. It seems quite odd and unfortunate.
Hereâs my suggestion. Move the client relationship up to the team level and use tasks instead of sub-task. The sub-task can then be used for the detailed actions taken to solve the issue. Ask you clients to submit a form instead of creating a task. Write your form so that it is directed to the right process using the rules. Sub-tasks are a danger zone when relying on process or reporting.
With the recent update to subtasks in mind â is there a possibility that rules will work with subtasks in the (near) future?
Hi there Marie. Iâm looking at a similar problem. Can you describe more fully what you are suggesting here? I canât quite wrap my head around it.
Hi @greer
No worries, Iâm happy to develop a little on this!
Rules currently donât work with subtasks because subtasks donât automatically ineharate their parent task attributes (and their project more specifically). Instead of using a Task > Subtask hierachy, I was recommending to use a Section > Task hierarchy (with Section replacing the task level, and tasks acting up as subtasks). This is just a workaround to be able to leverage Rules in a workflow that involves multiple actions to complete a single task. Again, this was just a workaround to explore, not a direct solution to the problem exposed by Chris!
I hope this helps to clear things up but let me know if you have any follwo-up questions!
That makes lots of sense, got it, thanks!
But couldnât you add the ability for some rules with subtasks? Like add to a project on creation or new comment?
Hi @Chris_Labatt-Simon, itâs currently not possible due to technical constraints, but definitely something weâre keeping in mind for future improvements!
This would be a nice feature to be able to automatically add subtasks to a task created in a specific project.
However this would be unecessary if it were possible to create a task from a template. This template could then have the desired âstandardâ subtasks.
My perspective is in mechanical design and I have a task to design a machine. There are certain things that need to be checked before I send the machine off to manufacturing regardless of which machine it is. It would be nice if I could have this âchecklistâ to be generated automatically when I start this task.
If
I 100% understand that some rules shouldnât/canât be applied to to subtasks. But at the very least, the âStatus Changed -->Complete Taskâ and âCompleted taskâ>Status Changedâ Rule should be made available to subtasks. Minimizing the steps my team has to take make sure âall the boxes are checkedâ would be incredibly helpful.