Permissions

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

We'll soon be introducing some changes for plan access in Portfolio for Jira.

When these changes are implemented, the following will be able to access all private plans: users with the Portfolio for Jira administrator user permission, users with the Jira administrators global permission, Jira administrators, and system administrators.

We recommend you start ensuring that your private plans are not displaying any confidential data. See JPOSERVER-247 - Getting issue details... STATUS for more details.

As a Portfolio for Jira administrator, you can choose the users who can make changes in a plan, and the users who can only view a plan.

Sample plan permissions

The permissions in Portfolio for Jira take precedence over the permissions in your Jira instance. This means that even if you're a project administrator in Jira, you'll still need specific permissions in to perform specific actions with the plans in Portfolio for Jira.

The following plan permissions are available in Portfolio for Jira:

Plan permissionView planEdit planModify issues in planDelete plan
Edit(tick)(tick)(tick)(tick)
View(tick)(tick) (only for specific actions)(tick) (only for specific actions)(error)

There are also other permissions in  Portfolio for Jira  that you need to consider, when configuring plan permissions.

PermissionDetails

Portfolio for Jira administrator

Can perform all administrative functions in Portfolio for Jira, including accessing any private plans.

By default, Jiraadministrators are automatically made administrators in Portfolio for Jira.

Portfolio for Jira user

Can perform the following actions:

  • Create plans and programs.
  • View plans and programs that they have access to.
  • For plans they can access, edit the issue sources, and edit any issue details.
  • For programs they can access, edit the name of the program, and the plans added to the program.

Note that this permission at both the program level and the plan level are independent of each other. This means that even if you can edit the 'Mobile expansion' program, you'll still need this permission to view and add the 'Beta' plan to that program.

Portfolio for Jira restricted user

Can perform the actions available to Portfolio for Jira users. However, users with this role are not permitted to update issues in Jira projects from within Portfolio for Jira.

Portfolio for Jira viewer

Can perform the following actions:

  • Browse and view plans in read-only mode.
  • In Jira, update parent linksteams, and target dates of issues.

Note that this permission at both the program level and the plan level are independent of each other. This means that even if you can view the 'Mobile expansion' program, you still need this permission for a particular plan to view that plan in the 'Mobile expansion' program.

Portfolio for Jira Labs

Can access and use the features of  Portfolio for Jira that are in Labs mode

Shared team management

Can access global team management and edit teams that are shared across plans and programs in Portfolio for Jira

Managing plan permissions

  1. In your plan, click settings () > Configure > Permissions.
  2. From the Edit drop-down, choose the users who can make changes in the plan.
  3. From the View drop-down, choose the users who can only view the plan.
Last modified on Jun 13, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.