Within Plans, how do I limit who can push changes to the included projects?

[Christi Heatherly]

Within Jira Plans, we have a need to keep our creators and editors from being able to "push" their updates to the projects.  

For instance, for a Corporate Initiative, we have the work pulled in by Parent.  Our organizer then will create a scenario to put in different dates or teams or etc....  I need to keep the organizer from being able to save those updates where they go back to the contributing Parent and work items.  

I thought we had this limited by creating a user group that only has access to the Plans User and Plans Viewer group.  Only the system admins had the top level rights.

Today, we watched a Scrum Master make an update in a Plan and push to a different team.  Could this be because he is an admin for that team and that supersedes the Plan permissions?

Or has the permission scheme changed for Plans?

[Trudy Claspill · Accepted solution]

Hello @Christi Heatherly 

Referring to the documentation for permissions in Plans:

https://support.atlassian.com/jira-software-cloud/docs/set-permissions-in-advanced-roadmaps/

...there is no role or permission specifically to block the ability to push plan changes to the issues they reference. If the users have appropriate permissions to modify those issues directly, and permission to modify the plan, then they will be able to push the changes in the plan to the respective projects/issues.