Can you set to let certain user only view and edit the tasks assigned to them in JIRA Server

[CECILIA ZHENG]

We have a project set in Jira server, but sometimes we need 3rd party agency to help us with a small amount of tickets. 

In that case, We want to give them permission to work on these tickets assigned to them only but not able to view the rest of tickets, can we do that in Jira Server?

How can we set that up?

[Trudy Claspill]

Hello @CECILIA ZHENG 

In your post you said "Jira Server", but your post tags indicate you are using Jira Cloud. Are you using Jira Cloud or Jira Server?

If you are using Jira Cloud, what type of projects contain the issues?

There would be two steps you would need to take:

1. Granting them access to the specified project while ensuring they don't have access to any other project.

2. Setting up Issue Security so that within the specified project the users could see only the issues assigned to them.

The details of both of these steps depend on the types of projects in use in your Jira instance and the type of the specific project you want the 3rd party agency users to access.

[CECILIA ZHENG]

Sorry for the confusion, Trudy!

My company used JIRA Server, and I have this account set personally before I join the company. So I am asking how to implement in JIRA Server.

Thanks!!

[CECILIA ZHENG]

And for the issue security setup, I want to make sure my team still be able to view and make edit on all tickets.

Just make the agency team view/edit based on their assignment.

[Trudy Claspill]

To restrict viewing of tickets in an individual project you will have to set up an Issue Security Scheme for the project with Issue Security Levels.

https://confluence.atlassian.com/adminjiraserver/configuring-issue-level-security-938847117.html

You'll need to have User Groups or Project Roles defined that include all your internal team member and exclude all agency team members

Define a security level that includes all those User Groups and Project Roles, and also includes Assignee.

As long asl the Groups and Roles you specify include all your internal team members and do not include agency team members, then the agency team members will see only the issues to which they are assigned.

You will want to select that security level  as the Default for the Issue Security Scheme. Then associate the Issue Security Scheme to the specified project.

By setting the Issue Security Level as the default, it will be set for all newly created issues in the project after that. However, no update is made to existing issues. You'll have to set the security level for all the pre-existing issues to limit their visibility. If no security level is set for an issue it will be visible to all users with the Browse Projects permission in the project.

You will also have to add the Security Level to the screens for the issue types in the project.

If you have not worked with Issue Security before I recommend that you set up a test project with a few test issues and the permissions and role assignments the same as the target project. Work out the security level configuration with the test project before applying it to the target project. If you don't set it up correctly you could unintentionally hide all the issues from all the project members.