# Use Linear to prepare an assignee change without scope growth

Example: A lead approved reassignment of an issue. A different comment suggests adding another feature to the same issue.

By Righthand Team · 2026-10-20

Source: https://www.righthand.ai/blog/use-linear-to-prepare-a-assignee-change-without-scope-growth

Keep Linear as the source for its records. A Righthand can use available information for the decision below.

This article is from Righthand. The example and result are illustrative. This guide has no executed integration test.

## The customer task

A lead approved reassignment of an issue. A different comment suggests adding another feature to the same issue.

[Provider documentation](https://linear.app/developers/graphql). The documentation gives information about GraphQL queries and mutations for issues. To create an issue, the intended team and supplied issue information are necessary.

## Make account access explicit

If Linear is available in [Connections](https://docs.righthand.ai/guides/adding-your-first-connection), connect the intended account. Give the Righthand access to that connection.

Provider documentation does not establish installed Righthand operations. Examine the connection’s available tools before assigning direct account work.

For direct account work, the connection must have the necessary read or write operation and permission. If that operation is unavailable, supply the information in a message. The owner must make any account change in that case.

[Connection Permissions](https://docs.righthand.ai/guides/add-a-connection) gives information about account access and tool permissions. Give only the access necessary for the identified task.

## The request to the Righthand

> Read the supplied reassignment approval.
>
> Prepare the assignee change only.
>
> Send the feature proposal as a different decision.
>
> Send the owner the result before 3 PM Friday.
>
> Use Pacific time.

## Use the provider records for the result

Identify the team and issue before reading or writing. Keep proposed issue edits distinct from completed edits. Use the owner's accepted scope for any mutation.

Reassignment permission does not give approval for a feature commitment.

For a permitted write, examine the resulting account record. A proposal does not establish a completed change.

For an external message, identify the recipient and permitted task. **Ask** uses an explicit instruction or approval. Connection tool permissions are another required control. [Communications Policy](https://docs.righthand.ai/security/external-communications).

## An illustrative result and next step

> The proposed update changes the assignee. The new feature remains outside the accepted issue scope.

The lead gives approval for the narrow update and gives a decision about whether to create another feature task.

## Try one account task

1. Give the Righthand one identified source record.
2. Compare its result with that source.
3. Examine the account record after a permitted write.
4. Examine the work in [Activity](https://docs.righthand.ai/guides/working-with-your-righthand).

If a direct operation is unavailable, give the source information in a message. This does not establish a direct integration.

## When the account tools are sufficient

Use Linear directly when its existing view gives the complete answer and no other conversation is necessary. A person can make the decision from that view.

[Compare plans](https://www.righthand.ai/pricing). [Get a Righthand](https://teams.righthand.ai).