You can build a customization to circumvent this, but it is actually a security feature. If resource data rolled up, then assigning a resource to a subproject will give them visibility to all parent projects. They would see the entire portfolio and you would not be able to hide projects from resources that have a role in a sister project in the portfolio. Also when logging into Clarizen, they would only see the portfolio projects in their homepage (like a super user) and not the specific projects.
Post
FollowAdd Resources from Subprojects to the Master Project
When a subproject is added to a project, the resources on the subproject do not show up on the resource list for the master project. I think this should be changed. Is there a way to fix this?
Thanks!
Please sign in to leave a comment.
8 comments
Date
Votes
Makes sense. Can you offer some insight on the customization needed to change this?
Thanks!
You can create a workflow rule where when a resource is added to a project, that same resource object is added to the parent project if a parent project exists.
Thanks Josh. I assume that I would use the workflow rule to "update field". However, I can't figure out what field I should update. Can you shed some light on this?
Thanks!
Hey Ashley,
I had to implement a similar rule on a Clarizen org that I was working with.
What you will have to do (I think) is add a workflow rule on the Resource object (which can be found under all links, assignment). The rule should run whenever a record is created.
In the conditions for the rule to run test if the assigned work items parent project has a parent project, if it does run the rule.
For the action you will need to create a new object of type resource and set the resource field to equal the resource of the object that triggered the workflow and the work item to be the parent project of the parent project of the workitem referenced in the triggering object.
Once active the rule should the act to add resources to the parent project when they are assigned to tasks within the sub project. What this rule wont do is add resources to the parent project when a resourced sub-project is moved into it, off hand I'm not sure how one would implement this with workflow.
Hope that's somewhat helpful,
Douglas
Thanks Douglas! I thought I answered this one but the post must have not gone through. Instead of updating a field you are actually creating a new link between the work item and the resource table, so you have to use the New Object action and scroll all the way down to resources.
Thank you both! Josh, I can't find an option to "create a new object." Maybe I am missing something? We are happy to pay for this as a professional service if it is an option.
Thanks!
For professional services, please contact Roni, your CSM. However, in the Set Actions section, all you need to do is select New Object >> Resource. If you hop on an advanced Q&A, this should be quick to show as well.