nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to setup a Plan User to edit plan, but not edit issues in the plan (JIRA CLOUD)?

David Laine

In the documentation for JIRA Cloud - it says:

"It’s possible for a user to have the Plans user permission, but lack the permission to edit a project included in the plan. If this is the case, the user won’t be able to save their changes using the Review changes button."

I cannot find any further documentation that describes precisely how to do this. Can anyone advise please?

To be clear, I do not want to restrict users from editing issues directly within the jira projects - just the ability to edit the project issues from within the advanced plan

Comments

Walter Buggenhout

Hi @David Laine,

A Plan is a sort of sandbox. It pulls in data from Jira sources, which can be a board, a project or a saved filter. Once issues are in a plan, users can update fields, set start and end dates etc. Since a Plan is fundamentally a planning interface to plan across multiple projects or teams, changes are only stored inside the plan until they are committed (in bulk) to Jira.

When a user does not have edit permission in one of the projects included in the plan, this commit action will fail for the issues where the user lacks the necessary permission.

If you want to make sure a user can only view a plan, you can make that user a plan viewer. That should ensure the user can't make any changes to the plan.

Hope this helps!

David Laine

Thanks @Walter Buggenhout.

Yes, I am aware that the Advanced Plans are a sandbox etc.

My goal here was to allow users to change the contents of the plan, so filter issues in/out etc. but prohibit them from changing the issues source data - I was hoping that this was the same thing as the documentation snippet was implying that included in my earlier post. In that, with Advanced Plans have their own permissions - it allows for you to chop and change the content of a plan, but at the same time, if you need to, you can prohibit the issue contents from being edited via the advanced plan batch update.

If you also look at the JIRA server version of advanced plans permissions, it lays this out more clearly imo. in that it separates out the permission in the table to be able to edit the plan and edit the issues contained within it:

Configuring plan permissions | Advanced Roadmaps for Jira Data Center 3.29 | Atlassian Documentation

If my interpretation is incorrect and it does not separate this ability, fair enough - I was just trying to establish this.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

permission

advanced-roadmaps

edit