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
Hi, the Permissions documentation for Jira for Portfolio states that a user only needs Portfolio for Jira viewer access to update parent links on Jira Issues. However experimentation tells me they need Portfolio for Jira user access.
Has anyone else bumped into this issue?
I don't like having to give everyone Portfolio for Jira user access as I do not want them creating plans - given that they get to set the scope of the plan the may accidentally change someone else's work.
Hi @Warren Rowe ,
Thanks for reaching out and the documentation you linked is the Portfolio for Jira Server version, and you have added the Cloud tag to this post, and there is going to be a slight deviation in the feature set in this case depending on the base platform.
The cloud version documentation for permissions can be seen at:
As covered in the cloud version of the doc and as you have been seeing in your tests the Viewer role is a read only option for portfolio and you would require the editor permission to make any changes to the portfolio specific functionality.
You are correct I am using Cloud. I took the snip form the Server version because the description of the roles is clearer (of course they may/will not apply for my Cloud instance).
The article you reference is about setting plan permissions. I am OK with these permissions.
My issue relates to users not being able to set a Parent Link in Jira (outside of a portfolio plan). Obviously this only relates to Issue types that I have defined as part of my (global) Portfolio hierarchy).