We are currently using Jira Portfolio V3.7.0.
A user without the Schedule Permission on a Jira Project tries to create an Epic in this Project from a Portfolio Plan and tries to commit the change to Jira but gets a message saying changes cannot be saved. A warning triangle appears next to the issue on the Review Changes Page and displays message "Make sure that you have Permission to rank issues". User does have the "Create Issue" permission on the Project.
The issue still gets created in Jira but still remains on the "Review changes" page showing the "Rank" under what's changed.
Why does the issue still remain on this page even though it's been created in Jira?
I think that @Walter Buggenhout _ACA IT_ has made a good suggestion for the reason the change isn't being saved, but to provide some context on what's happening there are actually multiple operations that happen when a new issue is created from a plan ... the issue is first created and then other attributes are set. So it looks like part of the operation is completing but because the ranking change is failing it still remains as a pending change. It's definitely worth looking at the permissions, however I also noticed that you're on quite an old version of Portfolio and would recommend upgrading to a more recent version. IIRC we did have a few problems with the review changes and commit process and it's possible that we might have ironed some things out by later releases (the latest version is 3.29.6)
Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events