Hi I know custom fields only affect the main task and direct subtask UNLESS you add to the project. However I am creating this on a template and when adding the subtask subtask to the project, the custom fields do not automatically appear. Is there a way to manually get them to appear?
I don’t think custom fields are inherited by subtasks.
What are you trying to accomplish, and why?
Wasn’t trying to get them to inherit. Just trying to set custom fields on a template on a subtask’s subtask. We have templates that can get deep into subtasks. Rather than the user manually having to set the custom fields manually on the subtask’s subtask, ideally it should already be set within the template (like you can do on the main task and direct subtask)
@Brandon_Olafsson1 I see. I tested this, and indeed when I get to this level I am unable to see or add custom fields. @Vanessa_N is this expected behaviour?
What I would recommend as a workaround is not to go so deep, also because the deeper you go with subtasks, the easier the work is missed.
An alternative might be to set the initial subtasks up as tasks, and have them blocking the main task with a dependency instead of having them be actual subtasks.
That said, the simpeler you can are able to keep your template, the easier it is for the users, which generally gives you the best results.
Right! Subtasks only inherit a project’s custom fields one level down from a parent that’s associated with that project.
To be clear, with inheriting you mean the fact that it has the same fields, not the values.
Stopping inheritance one level down seems like an odd choice.
Correct! Thanks for clarifying that distinction.
I know at one point they worked on having it at all levels and things got really messy technically so they abandoned the effort at that time. (This was a while ago; no idea what may have transpired since then.)
Hi @Jan-Rienk and @Phil_Seeman, thank you for tagging me. Phil is correct, and currently, only the first level of subtasks will inherit the project’s custom fields. Unfortunately, we do not have any plans to change this in the near term.
@Vanessa_N Although it’s not the reply I’d hoped for, thanks for letting us know.