If I try when logged in as the admin user it works fine, but when I'm logged in as a non-admin user that is in the Project Manager group I get the following error:
Field(s) `project_escalation_id` failed against a constraint: Error! You cannot assign escalation to the same project!
The requested operation cannot be completed due to security restrictions. Please contact your system administrator.
(Document type: project.project, Operation: read)
I have tried setting the Project Escalation field to a different project or leaving it blank and I still get the same error.
I just figured it out. Annoyingly if the Privacy / Visibility setting for the template is set to "Private project: followers Only" this error occurs (which I think is a bug). If you change that setting to Internal or Public Project, then the the new project gets created from the template fine.
We use the Private project setting a lot to avoid having other users lists of projects being cluttered with projects that aren't relevant to them, so I guess we'll just have to work around the bug by changing the setting and changing it back.
Please try to give a substantial answer. If you wanted to comment on the question or answer, just use the commenting tool. Please remember that you can always revise your answers - no need to answer the same question twice. Also, please don't forget to vote - it really helps to select the best questions and answers!
About This Community
|Asked: 3/22/16, 10:20 PM|
|Seen: 283 times|
|Last updated: 7/27/16, 7:10 PM|