does anyone find it necessary to use custom fields on subtasks? We currently develop our projects to be main task page and subtasks. We avoid developing further subtasks. Using custom fields (especially numerical fields) seem to be important for us in subtasks as we track time and cost. Does anyone have the same need? or are there other ideas?
We haven’t gotten custom fields yet in our Asana :(, but we would definitely want it on subtasks. We try not to create too many projects so a lot of our internal engagements (projects) are actually Asana tasks. The Asana project we usually call the pipeline (example: Sales Pipeline). So we tend to do what Asana expects to be done at the task level in subtasks. We do try to go down only 1 level though.
Great news! Custom fields are coming to all customers on Thursday (keep an eye out for announcements).
Today, custom fields are only defined project by project, so you would need to add the subtask to the project you want it to inherit fields from.
@RashadIssa I’ve been adding all costing tasks and subtasks into a central Time Tracking project for myself, and that gives them the Time fields (allocated and actual). It’s not an ideal solution, but it’s working right now for tracking time across my projects (without adding it to each project) and also for tasks/subtasks.
The other option would be to up-level subtasks to become tasks in the project- is this a possibility?
I like this idea, it would be nice to have the option to further sort and categories subtasks with custom fields
Yes, I can certainly house them in different projects to enable the custom fields. That would be the best solution for the time being. Moving them from subtasks to tasks would not work with the work flow that we have currently. If (or hopefully when) they get launched for subtasks, this will enhance the way we track and report on different progress items within subtasks too!
We desperately need subtasks to have custom fields. It is not feasible to have subtasks elevated to tasks and then elevate tasks to projects. Especially whilst dependencies are such painful process.
@Sean_Sullivan thanks for this feedback. What kind of workaround do you use to solve for this now? And what is your main goal in adding custom fields to subtasks / in what circumstances do you see this being most useful?
@Alexis Thanks for responding so quickly. The workaround is a PM, a call, or a scream if it is missed.
One Custom Field we use is Priority. If we were to elevate sub task to tasks and tasks to projects we would have over 1000 projects to filter through.
As dependencies as so unwieldy and convoluted to assign we can’t rely on them either. This process needs to be Leaned up.
Thanks for adding that detail, Sean! This will be helpful for our team to know as we find ways to approach the issue.
So, it sounds like you don’t really have a workaround for adding priority to subtasks right now? I suggest you try naming conventions, so at the beginning or end of a subtask you use the abbreviation P0 / P1 / P2. Do you think that could help you?
I had a client who needed custom fields on subtasks and we did the following:
Create a new project called "Custom Fields [not in use]
Add the desired custom field to this project.
When a subtask is created, use the “Add to project” option in the … menu to add the subtask to this project.
Now the subtasks inherit the custom field from this project.
It’s not ideal, but get’s the job done.
Our customers are thousands of Asana teams that use our Gmail/Outlook to Asana app on Asana’s apps page https://asana.com/apps/?category=communication. Having worked with many Asana teams, we see a common use case for why custom fields are needed on subtasks. And, we ourselves use Asana for managing customer service and product requirements for our releases.
Product Release Management
- Our Asana Product team is organized into projects like Bugs, Features, Integrations, etc.
- Let’s say there’s a feature such as “Reply in Asana to respond to an email” (we do that )
- The custom fields is Stage = In Progress, Completed, Tested, Failed Test, etc, or Priority.
- A subtask may be “Automatically cc all team members when I reply to a client”
- We have a different priority for each subtask.
- So now, we have to use a workaround to tag these subtasks with labels like “P1”, “P2”.
- And so, our starred advanced searches don’t show “All tasks and sub-tasks with a priority…”
- Many of our Asana customers create a team called “Customer Service”, and then have projects like “Paid Customers”, “Prospects”, “Inactive Customers”. In each of these projects, each task belongs to a customer. And they tag (rather, our Gmail/Outlook integration automatically tags) each task with the customer name, ex. “Ocean Cyclery”. Then, within that task, they use sub-tasks for a variety of reasons, and they want to see the same custom-fields as the parent task, mostly to do with prioritizing one request over the other.
There are, of course, workarounds. And the Asana team has to balance many competing requirements. So whenever they get to this, it will be helpful. Personally, it is the kind of feature that product teams really need most, so it’s a P2 for us.
Yes definitely on subtasks and also on My personal tasks. I’d like to add custom fields to my personal view.
@paulminors we are using this now as well, not ideal as you say, many more steps to complete.
It is working OK, but with any work around there is a chance for process failure with additional steps. Training lower level staff has been a challenge.
I have a service organisation and we do need to use custom fields in subtasks. I am desperately looking for a solution or a workaround that doesn’t involve creating 1000 other tasks or projects… looking forward to an ideal solution.
It just makes logically sense that a taks leads to another subtaks and that subtask needs to have the option to have customized fields as well, because it is just another task that we call a subtask.
May be there can be a feature of ‘prioritizing’ task. Where the head task is ranked as 1 and the following subtask is ranked as 1.1 (so there is a link). And what about as subtask requiring a new subtask? Than this would be 1.1.1…
So my best guess is, that the system of tasks and subtask might just be seen from a different angle, with prioritizing them, but handling them as normal tasks…
I hope my input might help to give a good angle for Asana developers… If this problem would be solved, my world would be completely different
I like the idea of having the subtasks numbered too. This will be a good indication for sequential activities.
We aren’t able to release a specific roadmap with timelines, but we are discussing the idea and prioritizing it among other feature requests.
This is an absolute must-have. I struggle to understand why this would be difficult or time-consuming to implement, given how independent from each other tasks and subtasks in Asana are.
@Alexis - any updates as to whether the feature is on the roadmap?
Also, probably worth combining (and summing up the votes) with this (identical) request: Custom Fields in subtasks
Are custom fields available for subtasks? I can’t seem to get that to work. Thanks!
Here is your answer
If you’d like to add custom fields to a subtask, the subtask must first be manually added to a project.