Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,338
Community Members
 
Community Events
176
Community Groups

How to limit access to commit changes for portfolio plan

Edited

Receiving an error of unable to commit, you do not have permission to edit issues in this project.

 

This is for when i am trying to commit changes to a portfolio plan.

 

Looking at the projects permissions schemes, the user has access to create/edit tickets, so what setting is needed in order to be able to make this change?

1 answer

0 votes

Hi Christopher,

Per the error message "you do not have permission to edit issues in this project" but the Edit action is not limited to just the Permission Edit issue, but can be part of other actions such as the Assign issues permission when setting an assignee, or the Schedule Issues permission if modifying due dates, and the Manage Sprints permission if you are attempting to add the issue to a sprint, and Link Issues permission if you have added a dependency.

This error is commonly triggered by one of the plan options via the "Commit of Changes" setting being enabled (set to "ON") and not having the assign issues project permission as this is causing an edit conflict where the noted setting is attempting to set the assignee value:

If set to 'On', assigning a single team member to an issue in the plan will also update the issue assignee in JIRA upon committing your changes.

I would recommend checking the fields that are being edited, and making sure that you have permission to complete all the actions within the project.

Regards,
Earl

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events