You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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 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)
No, if you discard any changes from a plan it will have no impact on the issue in Jira... ultimately the "source of truth" is the issue data in Jira, not the plan.