Release Management - need a repeatable template

Isaac10
Giga Expert

We have a project that will encompass many smaller projects. Each of the smaller projects has the exact same group of tasks, with some dependencies among them.

I would like to build one, repeatable, template of tasks that can be duplicated for each project. The only way I can think to accomplish this is with PPS:

  • Create a Project
  • Create all these tasks as TASKs
  • Create Dependencies and populate assignment groups

Is this the best way to do this? Can anyone help with a simpler/easier way?

Thanks everyone!

Isaac

1 ACCEPTED SOLUTION

Sean Witt
Tera Guru

Hi Isaac.



Since each of the smaller projects has the same set of tasks, maybe consider:



1) Building a project once to reflect this set of tasks.


2) Save it as a project template.


3) Create as many additional projects as you need, applying the template, so that they all have the same shell/starting point.


4) Create your master project that covers all of the smaller projects, do NOT apply the template for this one.


5) Make all of the smaller projects sub-projects on the master project. You can do this from the tab/related list for sub-projects on the master. So the project contains sub-projects, the same way a "regular" project contains project tasks.



That way the bulk of your work is just building the project template once, and then your single parent project ties them all together. Does that make sense?



Sean


View solution in original post

5 REPLIES 5

Goran WitchDoc
ServiceNow Employee
ServiceNow Employee

Well, you can do this with a workflow. find the conditions to make it only trigger on the smaller projects and build all the tasks etc. in there.. then it will run each time you create one of the smaller projects. If I understand your requirements correctly.


Huh, that's an interesting idea. Thanks for that!


It's easy to forget the workflow engine 😃 Normally you just think of it for Service Catalog and perhaps change/knowledge . But when you mention repeatable... that is a flag for workflow


Sean Witt
Tera Guru

Hi Isaac.



Since each of the smaller projects has the same set of tasks, maybe consider:



1) Building a project once to reflect this set of tasks.


2) Save it as a project template.


3) Create as many additional projects as you need, applying the template, so that they all have the same shell/starting point.


4) Create your master project that covers all of the smaller projects, do NOT apply the template for this one.


5) Make all of the smaller projects sub-projects on the master project. You can do this from the tab/related list for sub-projects on the master. So the project contains sub-projects, the same way a "regular" project contains project tasks.



That way the bulk of your work is just building the project template once, and then your single parent project ties them all together. Does that make sense?



Sean