- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Hi guys, I just joined this SIG group and I am happy to share thoughts with you!:)
To start off, here is something which I was fighting with lately, in case any of you has had similar needs. I was trying to give some flexibility in our instance when it comes to creating and managing projects by enabling non PMs (regular ITIL users) to create and manage new projects. This was due to the demand that our PM team was limited in number and we had multiple projects moving in various areas. However, I wanted those non-PM guys to be able to edit only the project which they have created, not ones created by others. Governance of all projects remained in the PMs of course.
I managed to put together a solution for this in a combined brainstorming with few smart guys from the community. Here is what I did:
1. created a custom role, named it 'knowledge_creator'
2. created a bunch of ACLs for pm_project table (for read, write, create operations), as for 'write' I have the condition "opened_by IS javascript:gs.getUserID() OR project_manager IS javascript:gs.getUserID()"
3. created a bunch of ACLs for pm_project_task table as well, to enable the users with the custom role to create tasks from within the project.
It worked like a charm for us The users with that custom role are able to create projects and project tasks from that project, and able to edit only the projects which they have created, or for which they are marked as project managers.
I hope this could be of help to someone. Take care!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.