Setting up access rights for queues

Setting access rights for queues

By default, users are not restricted from accessing queue issues.

If you restrict access to your queue, only the users specified in the following fields will have access to its issues by default: Author, Assignee, Followers, and Access.

You can change access settings for individual users, groups, or roles:

1. Open the queue page.

2. To the left of the queue name, select → Configure.

3. Go to Access → All issues.

4. Add users and groups to configure access for:

   • Users and robots: Individual settings for individual users. To add a user to this category, enter the login or the user's name in the search bar at the top of the table.

   • Groups: Settings for all employees.

   • Roles: Settings for users who have specific roles in queue issues:

     • Access: Users listed in the Access field of an issue.
     • Follower: Users who subscribed to the issue.
     • Reporter: The person who created the issue.
     • Assignee: The person assigned to the issue.
     • Queue owner.
     • Queue team members: Users added to the queue team. This role isn't on the list by default, but you can add it via the search bar at the top of the table.

5. Set permissions for queue actions:

   • Create issues: Users are allowed to create new issues in this queue.

   • View issues: Users are allowed to add comments to an issue and change its status, but not to edit issue field values.

     Note

     To bulk change multiple issues' statuses, view permissions are not sufficient. This requires permission to edit issues.

   • Edit issues: Users are allowed to comment on an issue, change its status, and edit issue fields (such as changing its deadline, adding followers, and so on).

   • Queue settings: Users are allowed to edit queue settings.

6. Click Save.

If a user has multiple roles, they gain all access rights associated with each role.

Example

If a user is both the reporter and assignee, they are allowed to Create issues, View issues, and Edit issues.

Adding a message for users who can't access issues

When a user is trying to open an issue from a queue that they don't have access to, a message saying Contact the queue owner pops out with the owner's name specified.

This message can be changed. For instance, you can specify another user with queue admin rights who can give access to issues. You can also specify the reason for restricting access to the queue.

To edit the message displayed to users with no access to the queue, do the following:

1. Open the queue page.

2. To the left of the queue name, select → Configure.

3. Go to Access → All issues.

4. Under Message for users without access, click Edit.

5. Write your message and click Save.

Setting access rights to issues with components

You can configure access to various components of the queue. This lets you create separate setups for issues that have components and those that do not.

To configure access to issues by component:

1. Open the queue page.

2. Add to the queue components to control access to issues with.

3. To the left of the queue name, select → Configure.

4. Go to Access → Issues with component.

5. Add users and groups to configure access for:

   • Users and robots: Individual settings for individual users. To add a user to this category, enter the login or the user's name in the search bar at the top of the table.

   • Groups: Settings for all employees.

   • Roles: Settings for users who have specific roles in queue issues:

     • Access: Users listed in the Access field of an issue.
     • Follower: Users who subscribed to the issue.
     • Reporter: The person who created the issue.
     • Assignee: The person assigned to the issue.
     • Queue owner.
     • Queue team members: Users added to the queue team. This role isn't on the list by default, but you can add it via the search bar at the top of the table.

6. Click Save.

1. To configure access to an individual issue that differs from the access settings for the entire queue, add a component to the issue.

If an issue has several associated components, all users with access to at least one of them will be able to access the issue.

If an issue has the Hardware and Software components, it can be accessed by users from both the Product development and Application development groups.