Hello, I have a template that I would like to edit to do the followin
What I’m trying to do: I have a custom field called “Regions” which include 14 regions used by a template at my org. I cannot auto-assign the region because it is used by many users, however once they select the Region for the Project (created from template) then I would like it to autopopulate as the “Region” across all tasks. I would also like all NEW tasks to import that same region.
What I’ve tried so far: I’ve tried to use the Automations to trigger this behavior but it says it cannot update across all tasks
Unfortunately, I don’t think there is a way to do this natively from a project template, the easiest workaround I can think of would be to bulk edit your task custom fields once the region has been identified, but that is manual.
Out of curiosity, what is the reason that you need the region displayed on each task? Just if I can think of a workaround dependent on the why.
The only other way I can think of would be to create a template for each region and they select the appropriate template, but that may be overkill!
Will be interesting to see if anyone else knows a way! Sorry I couldn’t be of more help.
I would encourage you to track Region at the project level, not the task level, because it’s an attribute of the project (kind of a header-level project attribute) and much easier to maintain that in a single spot than the overhead of maintaining in every task and risking something getting out of sync. You could encourage this by naming the project template “Project Such and Such ” which reminds users to name the project with the Region.
In terms of visibility of the task’s Region elsewhere (other than in this project, where it would be obvious by looking at the project name), you will always see this in the task’s detail pane where the project name is already shown. In list view of any project you can set Options > Hide/Show columns > Project and it will be visible alongside all tasks at once in a Project column without having to open the task detail pane.
If you also want to, you could indicate a portfolio in step 3 of the project template, and include the Region custom field in that portfolio so it can be set, project by project. It will appear as a column in the portfolio list view, and also in each project’s Edit project settings popup. But that’s not effective at showing it at the task level, which I explained above, but may be helpful for other reasons.
Without knowing the full workflow you’re trying to achieve and having an interactive discussion about it, that’s the best I can offer!
but by this logic wouldn’t he need to create 14 versions of the same template? That seems much harder to manage long term because ANY tweak to the template would then need to be manually done to all 14.
However, to your suggestion of using a portfolio field, I think is a segay into a badly needed feature- the ability to run rules off portfolio fields, or just have project-level custom fields in general (not associated with a portfolio specifically) that could be tied to rules.
I’m just recommending the same, single project template.
Sorry, a key part of my reply had special characters that the Forum swallowed, so let me correct that:
naming the project template "Project Such and Such <Region>" which reminds users to name the project with the Region that applies to this particular project.
I agree about the more flexible rules and I think that’s been requested in Asana Community > Product Ideas so you could vote on it there.