Hi - I recently noticed the new status update templates, which is something I’ve been eagerly waiting for; however, I can’t figure out how to use them for our work.
I’d like to create a status update template that project managers can use for any project in a portfolio and I’d like the name of the status update to reflect the name of the project and the day the update is posted, just like a normal status update. I have created a template (which, by the way, is far more complicated than the old method of creating a status update), but in order to save the template I have to give it a name, which then becomes the title of the status update each time. I don’t want to create a template for each project. Can someone tell me how to make this feature work for our use case? What am I missing?
Re the field “Status update for …” (aka Status Update Title), a Save is not allowed if this is empty which confused me, because the text value of this field would be set in each status report and appear as the Status Preview that shows in portfolios, and is not known or appropriate to set in the template. It would be very appropriate to use this field to indicate the model for others to use for their updates, like:
Monthly Update: <brief summary under ten words>
@Helen_Rabold1, I’ve deliberately not used this field for either the project name nor the status update date; both of those are automatically captured by Asana when you post your actual status update so it’s better to use this field for the one-line status summary instead.
For the “Template name” field in the far left corner, give a name for this template itself that will help others to know when to use it, particularly if you have more than one. To carry through my example, I’d expect a name like “Monthly Status” would work for this one, and maybe you’d have a different status template for quarterly usage.
Thanks, Larry. Yes, it’s the “Status update for …” field that I’m confused about. I might use your recommendation and just use the field as a model to indicate what I want the PMs to place in the field. In my testing, whatever I put in this status update title will pull through to the actual status update so I have to train the PMs (and cross my fingers that they remember) to remove whatever is in that field before posting their status update. Not super ideal.
Totally agree! @Emily_Roman is this on the roadmap or should we submit an enhancement request for this capability? For my team, the ideal state is that the status update template is a part of the project template and doesn’t need to be selected by project.
