Under Community Review

Project creator to auto-become Project Manager

We use the Project Manager field in projects to identify the PM responsible for the project and would like the ability to do the following.

1. The project creator (i.e. current user) to be automatically set as the Project Manager when creating a regular project

2. The current user to be automatically set as the Project Manager when creating an Automation Project rather than the project creator, which is the service user account for the automation connector.

I know it's possible to use project templates to set the project manager but when you have a team of project managers, this gets out of control.

Peter Johnston
Parents

  • Hi Peter, I'd like to clarify a couple of points with you regarding this request.

    For Point 1, in the absence of being able to set the "Project Creator" to be the "Project Manager", could you not just assign the relevant workflow tasks to the Project Creator directly for templates/projects where that behavior is required? From a permissions/project conversations perspective, there shouldn't be any difference between these two approaches. Is there any other functionality you would lose by handling this through workflow task assignment rather than using the Project Manager variable?

    For Point 2, how would we determine who the "current user" is for automation projects?

    FYI, we also provide an endpoint using Public API to retrieve/update the Project Manager variable for a project The functionality you are requesting could therefore be implemented as a custom workflow task if that is an option you may want to consider.

    Cheers,

    Ian

Comment

  • Hi Peter, I'd like to clarify a couple of points with you regarding this request.

    For Point 1, in the absence of being able to set the "Project Creator" to be the "Project Manager", could you not just assign the relevant workflow tasks to the Project Creator directly for templates/projects where that behavior is required? From a permissions/project conversations perspective, there shouldn't be any difference between these two approaches. Is there any other functionality you would lose by handling this through workflow task assignment rather than using the Project Manager variable?

    For Point 2, how would we determine who the "current user" is for automation projects?

    FYI, we also provide an endpoint using Public API to retrieve/update the Project Manager variable for a project The functionality you are requesting could therefore be implemented as a custom workflow task if that is an option you may want to consider.

    Cheers,

    Ian

Children
No Data