Hi all,
Is it possible to add rules on subtasks?
who is the creator of the task, automatically becomes the assignee of the subtasks of this main task. possible?
if ‘A’ is the creator of the task. then ‘A’ automatically assignee of all the subtasks created for this task.
P.S. I already searched and find out this is available for main tasks, but not available for subtasks, or maybe I missed something.
thanks
Hi @Omer_Buttt,
Yes you can, and you can use the same rule as for the main tasks. Just be sure to select the rule to run both on tasks and subtasks.
thanks for replay
I did that same but unfortunately, It only applies to the main task whenever I create a new sub-task, it is not applicable on that.
thanks
I am getting the same… That’s wierd 
Maybe another forum leader knows what is going on. @ambforumleader @pforumleader
I am not sure the “section is X” works for subtasks, did you take that into account?
@Bastien_Siebman don’t get it your point. can you elaborate, please?
if you talking about the section “QA”, so yes, I already making rules for subtasks under this same section and those are working perfectly fine.
I was pointing out a typical misconception about subtasks belonging to the project, and that could have caused your test to be irrelevant but looks it wasn’t useful in your case.
@Bastien_Siebman okay. so what do you think?
Any solution for that?
My experience tells me that we rarely see a bug in a case like this, but instead we misunderstand subtasks. Are we sure “task added to project” does fire for subtasks? I wouldn’t be so sure…
@Bastien_Siebman I’m not sure. but as we see on top right corner and as @Jan-Rienk mention that “Runs on Tasks on subtasks”. isn’t that mean that should work on subtasks?
I tried that after making a subtask I append the subtask to the project.then the assignee was set to the creator.
That says making a subtask doesn’t fire a rule.
“Task added to project” does not fire for new subtasks.
BTW for one solution, the “Task is newly created” rule trigger in our Flowsana rules does fire for subtasks. (In fact, we also have an option for a rule to fire only on subtasks, not top-level tasks.)
I tried that, but it also fires on subtasks that are “homed” to the parent task project without that selection.
And this is expected behaviour?
@Jan-Rienk - it’s the way it has worked during the entire existence of rules. Though, I hope it changes.
Yes, because a newly-created subtask is not attached to the project, so how could it be “added to the project”?
Please note I’m not advocating that this is a particularly helpful behavior, just saying that it does make consistent and logical sense given the way subtasks work by default vis-a-vis projects.
@Phil_Seeman what does that mean “because a newly-created subtask is not attached to the project”? subtask attached with the current project, right? Main task and then a sub-task. I think I misunderstood what are you trying to say.
I will try your flowasana solution. Hope it will work for my scenario(what I need).
Thanks
Also, I’m trying to make a rule on the custom field.
custom field was " bug reported by" (who is reported the bug, in easy words who created the subtask)
what I need is, that whoever created the sub-task, custom field “bug reported by” automatically changes with the same person who created the subtask.
Right now, I found that in the rules, you can manually select the people for this custom field, which I don’t need.
Thanks
