We couldn’t update the Assignee value.

[Piotr Niewinski]

When I try to change the assignee of a task which I created, which is currently assigned to me:

1. I select a teammate from drop-down list

2. I get: 

We couldn’t update the Assignee value.
You can try again in a few minutes, or refresh the page.

I'm the Team-managed space creator / owner. The guy is added as an Agent.

[Trudy Claspill]

Hello @Piotr Niewinski 

Welcome to the Atlassian community.

Did you try again later? Did you try refreshing the page?

Is another member of the project able to set the Assignee to that user?

Are you able to change the assignee to a different user?

Is the project/space Software, Business, or Service?

Can the person be made the assignee of an item in another project/space?

Has that other person been granted a license to use the Jira instance?

[Piotr Niewinski]

I tried many times.

I didn't ask anybody else. It is my project and wanted to assign task to other user, which I see in a dropdown list. This user works with other Jira projects in our company.

I tried with many other users and I found only two that were not raising this error.

Team type: Software Development.

Can the person be made the assignee of an item in another project/space? - Yes

[Trudy Claspill]

For clarity can you find the Project/Space type by clicking on the ... button next to the name in the panel on the left, and get the information from the bottom of the pop-up?

You said the user can be made the Assignee of other items in other project/spaces. In what types of project/spaces can they be made the Assignee?

You mentioned that the user was added as an Agent. Can you provide a screen image showing where the user was added as an Agent for this project?

If the project/space type is Team-managed Software, the native Agent role is not applicable. At the application access level the Agent role applies only to the Service project/spaces which are part of the Jira Service Management app.

It is possible that there is a custom project role named "Agent".

Adding the user to a Role in the project may not be sufficient to enable them to be set in the Assignee field. A user has to be licensed for the product for that type of project/space (Jira Business/Software vs. Jira Service). They user has to have appropriate an appropriate application role. The user has to have access to the project, and the method for that differs between Team Managed and Company Managed. The user has to have the permission associated with being an Assignable User, which also differs between Company and Team Managed projects.

[Piotr Niewinski]

For clarity can you find the Project/Space type by clicking on the ... button next to the name in the panel on the left, and get the information from the bottom of the pop-up?

As I wrote earlier: I'm the Team-managed space creator / owner.

You said the user can be made the Assignee of other items in other project/spaces. In what types of project/spaces can they be made the Assignee?

There is a company-managed space, where that user can be assigned.

You mentioned that the user was added as an Agent. Can you provide a screen image showing where the user was added as an Agent for this project?

Space settings > Access > People and access > ... he is an Agent here



If the project/space type is Team-managed Software, the native Agent role is not applicable. At the application access level the Agent role applies only to the Service project/spaces which are part of the Jira Service Management app.

It is possible that there is a custom project role named "Agent".

It is available there and I haven't created such.

The user has to have the permission associated with being an Assignable User, which also differs between Company and Team Managed projects.

That may be the key. I will ask my IT. Thanks!

[Trudy Claspill]

As I wrote earlier: I'm the Team-managed space creator / owner.

Actually, you said "Team type: Software development". The pop-up contains 2 pieces of information; Team-managed and Software|Business|Service Space. Both pieces of information are important. And we often see terminology misused, which is why I asked for the information specified in the pop-up.

There is a company-managed space, where that user can be assigned.

That verifies that the user has some sort of license for the Jira instance, but we don't know if it is a Jira license, which would support access to Software and Business spaces, or a Jira Service Management Agent license, which would support access to Service Spaces.

Space settings > Access > People and access > ... he is an Agent here

That indicates the user was assigned to a Role in the project. The "Agent" role is built in to Service projects. If this is a Service project then the user is going to need a license for the Jira Service Management application (versus the Jira application) To be able to be set as the Assignee for issues in a Service project. That license would need to be granted by an Organization Admin or User Admin.

If the user only has a Jira application license and is assigned the Agent role in a Service project, that makes them a Collaborator in the Service project. Collaborators have limited access in a Service project, and that does not include being able to be an Assignee. For more information refer to this document:

https://support.atlassian.com/jira-service-management-cloud/docs/what-users-and-roles-are-there-in-jira-service-management/