Hi
What I’m trying to do. Just a week or so ago, I was able to create a rule that, whenever a form is submitted, would create sub tasks and assign task types to those sub tasks. The task types getting completed were the triggers to the workflows and follow up sub tasks I had set up after wards.
What’s not working or confusing. It seems it’s greyed out here in the screen shot,
Has anyone else noticed this? Is this a bug with a new update?
Hi Kristopher, welcome to the community! Thanks for flagging this.
A couple quick checks that usually explain why “Task type” is greyed out for subtasks:
Is Task type a project field in your setup? If so, the subtask needs to be in that same project to edit the field. Subtasks aren’t automatically in the parent task’s project, so the field will appear disabled until the subtask is added to the project.
If you’re using a rule to add subtasks, make sure those new subtasks end up in the project that has the Task type field. Once they’re in the project, the field should be editable and rules can set it.
Simple workaround:
If you’re sure the subtasks are in the right project and it’s still greyed out, can you share:
A screenshot of the rule step where you create the subtask and try to set Task type
Whether Task type is the native field you use in that project or a custom field
Confirmation that the created subtasks are in the same project as the parent task
I’ll pass this on to the team so we can double check if there was a change here. You can also add visibility in Product Feedback here: https://forum.asana.com/c/forum-en/product-feedback/20
For what it’s worth, it does appear there was some sort of change here @Iren_Vilaniso.
I have an old rule that created a subtask and was able to set the task type when I originally made the rule, but now I cannot update it (see below). The logic seems to think if you want to adjust this you must be trying to add approvals as opposed to a custom task type.
Can you confirm the functionality has changed?
I’m running into the same issue. I was previously able to make subtasks custom task types, but I’m seeing the same thing where it’s grayed out when selecting the task type.
We’re experiencing the same. Task type selector is grayed out. Why?
Hi @Peyton_Lee,
Wondering if you might have some input here, as it does appear to be a recent change, as @Skyler pointed out?
A few months ago, I set up a rule to add subtasks automatically to new tasks in a project. When I did this, I set the “Task Type” to a custom task type we had called “IT Task”. I went in today to add another subtask, and all new subtasks are forced to the genetic “Task” type, and the field is greyed out and cannot be changed. My subtasks from a couple of months ago are still my custom “IT Task”, but all new tasks are stuck on the generic “Task” type.
I have tried creating a new rule, and even in a different project and portfolio, but the issue remains. I have ensured I am an admin. What is the problem and how can I fix it?
I’ve tested it on my end. I can still create all subtask types - task, milestone, and approval.
@Cory_Wallace, FYI I merged your post with an existing one on this same topic.
(@Stefan_Kirilov, Cory was referring to custom task types, not the task/milestone/approval distinction.)
Thanks - sorry, I searched and didn’t find this one.
Any updates on this? Seems like a bug, potentially introduced with a new feature?
I pinged the Asana PM on this, we’ll see if they or Stefan can provide any updates.
I just came across an issue that isn’t exactly the same, but seems may be related. I have some rules that we set up and use all the time that have suddenly stopped working. They worked yesterday (January 21st) and are not triggering today (22nd). The only change I can see on my end is that my previous “Customize” button in the upper right has changed to a “Workflow” button and now these rules aren’t functioning.
I can get into the specific rule details if needed, but I’m wondering based on the convo above if this is a broader “rules broken” issue rather than the details of each of these.
Thank you for any input/feedback.
Just thought I’d jump in here to mention that it appears that this issue has been fixed and it is now possible to create a custom task type using the rule actions to Create task or Create subtasks.
Only the Create approvals action does NOT support creating task types, which makes sense, however, that action seems a bit redundant now because you can create a mix of both Approval type tasks and Custom Task types as subtasks simply using the Create subtasks action.
Obviously, you need to add the custom Task type to your project so it will be available in these rule actions.
