Share an issue

Your Adobe Workfront administrator grants users access to view or edit issues when they assign access levels. For more information about granting access to issues, see Grant access to issues.

Along with the access level that users are granted, you can also grant them permissions to View, Contribute, or Manage specific issues that you have access to share. For more information about access levels and permissions, see How access levels and permissions work together.

Permissions are specific to one item in Workfront and define what actions one can take on that item.

Considerations about sharing issues

In addition to the considerations below, also see Overview of sharing permissions on objects.

A Workfront administrator can add or remove permissions to any items in the system, for all users, without being the owner of those items.
  • The creator of an issue has Manage permissions to it, by default.

  • You can share issues individually, or you can share several of them at a time. Sharing issues is identical to sharing other items in Workfront. For more information about sharing items in Workfront, see Share an object.

  • You can grant the following permissions to an issue:

    • View


    • Manage


    • Contribute

  • When you share an issue, all the documents attached to the issue inherit the same permissions.

    The Workfront administrator can specify whether documents should inherit permissions from higher objects in the user’s access level. For more information about restricting inherited permissions on documents, see Create or modify custom access levels.

  • You can remove inherited permissions from an issue. For more information, see Remove permissions from objects.

Ways to share an issue

  • Manually, which is similar to sharing any other object in Workfront. For more information about how to share objects in Workfront, see Share an object.

  • Automatically, by doing one of the following:

    • Specify the permissions on any of the parent objects of the issue: project, program, or portfolio. Issues inherit the permissions from their parent objects. For information about viewing inherited permissions on objects, see View inherited permissions on objects.

    • Add entities to Project Sharing on a template used to create the project the issue is on. For information about sharing projects from templates, see Share a template.

    • Specify the permissions on all issues in a project when you edit the project. For information about managing the access to issues or requests on the project based on a user’s permissions to the project, see the section in the article Edit projects.

      note tip
      If you don’t specify what issue permissions you want users to have when they are assigned to the issues on the project, they receive the same permissions they have on the project, by default.
    • Specify the permissions users receive on issues they submit in a request queue when creating a request queue. For information, see Create a Request Queue.

      note important
      Permissions are granted differently depending on whether or not the project is published as a request queue:
      • When a user submits a request to a project published as a request queue, the Primary Contact and Entered By users are granted the permission specified.
      • When a user submits a request to a project not published as a request queue, the Primary Contact (if different from Entered By user) is granted the permission specified, and the Entered By user is granted Manage permissions to the issue.

Issue permissions

The following table displays what permissions you can grant users when allowing them to View, Contribute, or Manage an issue:

Add issues
Attach Custom Form
Edit Custom Fields
Approve Issue
Add An Approval Process
Add Documents
Copy Issue*
Move Issue
Log Hours
Convert to Project*
Accept Assignment
Updates/ comments
Modify Planned Dates
Make Assignments
Share System-wide

*Controlled by the access levels and the permissions on the project.