Relationship between a Project and a Request

shill
Mega Sage

Has anyone created a relationship between a project and catalog requests?
Our Project Managers would like to tie a project to one or more requests that are submitted to actually do the work of the project.
Right now, they are creating a project task along with a request, but since there is no native relationship between them, they must manually manage the two records. (manually close the project task when the request is complete).

My thought is to add a field for a related request to the project task form so that we still have a project task (and gantt chart) for the project. Then setup a business rule on the request so when it closes, it also marks the project task complete.

Not sure if this is the best solution though, so I am asking for ideas.

Ideally they wanted a related list that combines both project tasks and requests into one, but there are so many differences between the two (planned start date being just one) that I don't see how that would work very well.

5 REPLIES 5

randrews
Tera Guru

we have a generic type of request that is a simple record generator... we use this for pw resets and other requests that aren't in the catalog... from that we have a ui action to create a project.. which sets a parent child relationship
_________________________
createProject();

function createProject() {

current.update();

gs.getSession().putProperty("firstam.request.id", current.sys_id + '');
gs.log('firstam.request.id: ' + gs.getSession().getProperty('firstam.request.id'), 'Cloud Sherpas');
var url = 'wizard_view.do?sysparm_parent=Create%20Project';

action.setRedirectURL(url);
}

________________________________

we had also considered a catalog item to request a project that would go to the pmo's.. they would the close that request when they opened the project.


shealyjs
Tera Contributor

Am interested in what you ended up doing. We have incident now, and are starting in PPM, and just added catalog. Until change and release come along, the project managers will interface w/ development exactly as you said, using requests. So we have the same need. What did you do? I was able (in sandbox) to add the Parent->Request list to the project, and when you create new from that list, it takes you to the catalog where you can   create the request, but the list isn't populated in the project, so I am sure there is more to it than that.


Joyce,


To be honest, we have done nothing currently to resolve this. This has not crept up our priority list yet, so it has been on the back burner for a while.There is the task relations formatter that you can add to the forms, but it only creates a relationship between the two records.



If we get any headway on an option, I will post an update.




What SN version are you on? Have you considered using Demand to capture requests?



And here is an oversimplified representation of how we have our inter-connectivity: Bunzl SN Turn to Project Flow - Google Drawings (doesn't show CHNG, etc.). Also check out slide 4 of this presentation I gave last month.


Here is how we have everything related: Requests for software changes, new software, upgrades etc. are a form within our ServiceCatalog and this automatically creates a Demand (DMND) record (of course the end user doesn't know this goes to DMND). We have a 'create project' and 'create enhancement' button on our Demand form, so when a Demand has gone through the approval process and is approved, certain people have rights to click on that button, and the PRJ or ENHC record is automatically created and certain fields are automatically copied over to the PRJ or ENHC (e.g., description, cost estimates, duration estimate, etc.). These forms remain tied together and you can see the relationship via the 'Related records' tab in the Project or Demand forms or by enabling Hierarchical Lists in list view. You should be able to easily go into a project and relate it to multiple Demands.



It sounds like this would be a drastic change from the process you were considering. Not sure if this is an approach your organization is interested in.



BTW, there is a PPM community you may want to check out.