Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Permission issues - updating Parent Links

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.

Portfolio for Jira.PNG

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.

1 answer

0 votes
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 02, 2019

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).

Dave explains my issue well:

Like Earl McCutcheon likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events