We have a situation where any user can add portfolio item type (theme, feature, etc.) We would like to limit this so users have to select certain portfolio items to map their features to instead of creating their own. How can this be done?
Permissions in Agile Central are set at the Project level so you can't really control this. Further, taking an action like adding a Feature to an Epic or other higher-level portfolio item actually causes an edit to the parent item so any user who needs to add or edit a user story or lower level work item that's attached to a portfolio item needs to have Editor permissions to the portfolio item.
We had similar questions early in our implementation but frankly we got good results simply by training users and doing a bit of auditing of newly created portfolio items early on. In my implementation of ~1,500 users we don't have any routine problems with portfolio items being added "incorrectly". If there's a specific use case that's giving you trouble then by all means discuss it further with the community here but security and permissions aren't likely to be the solution. Hope that helps.
Not the answer I wanted, but it is the answer I needed. I was trying to be proactive, but will train our users at the forefront.
Thank you very much,
Donna Evers, CSM, FLMI, CISA (expired 2016)
Sr. Business Management Analyst
Tools and Information
4321 N. Ballard Road, Appleton, WI 54919-0001
This message contains confidential information intended only for the above addressees and may contain information that is proprietary or legally privileged. If you received this message in error, please notify us and delete the original message. You must obtain permission from Thrivent Financial to use its logo on all materials. Failure to do so could result in legal action.