Ive just spent a good amount of time building out a group of projects within a team that all work together as a backend/frontend structure. Certain projects house the full set of tasks for a project, and they feed a more simplistic client facing “task manager” as due dates become available for collaboration.
These are for construction projects, so they can (and need) to be duplicated for each project that gets undertaken.
I want to be able to essentially duplicate at the “team” level so that the rule relationships stay intact.
Not only that, but also just to cut down on the manual task of creating new projects from templates a bunch of times every time we start a new project. Which will aloow just about anyone to create a new project and not just me or someone else that has to learn how to set the project up.
I know bundles were just released (for Enterprise only… ). And the spirit behind those seems to be in this vein, but appears to be limited to managing customization packages across a single project… not for deploying multi-project bundles…
Anyone know if this is a feature in the works, or if Flowsana can achieve this?
I cant imagine Im alone in needing to spin up “templated teams?” Have you come across the need for this use case in your travels?
Seems to me that it would be a natural feature, given the ability to multi-hone tasks across multiple projects and the ability to create Asana native rules that add/remove tasks from other projects.
More curious if its something that might be useful for a larger set of users.
I actually think the feature is available for some specific use cases and clients from specific verticals, so maybe this will be available to us all soon!
I absolutely need to be able to create “Team Templates” too!! We use “teams” per each corporate event we do, and to be able to duplicate the team with all the same projects and tasks would be a lifesaver.
If you can live with manually creating a team and manually moving the projects into it, you could create a ‘project creator’ project that could contain a single rule that could convert a task (named as your team project) into multiple projects based on their relevant templates. That rule could be built natively in Asana using the ‘convert task to project’ action which can simultaneously also add the projects to a portfolio as well as add the task’s collaborators as project members - very powerful.
But you can also use the Flowsana.net actions within the ‘External’ rule actions to do the same but additionally it can use variables to name all these projects based on the task’s name or its custom fields, for example project code numbers.
I Agree that the Templates use could use some work. Not only would it be useful to create more complex and complete templates so there is less onboarding involved in new Projects, but our template is always evolving, and I wish there were a way to upload tasks from an active project to the new template or to universally across the organization share a “task Template” so it doesn’t just show up in a single project
). And the spirit behind those seems to be in this vein, but appears to be limited to managing customization packages across a single project… not for deploying multi-project bundles…