> ## Documentation Index > Fetch the complete documentation index at: https://docs.protodesk.io/llms.txt > Use this file to discover all available pages before exploring further. # Create and update Linear issues with Evelin > Find, create, and update Linear issues, add comments, and check outcomes without accidentally repeating a change. Use Evelin inside a customer conversation to find Linear issues, create an issue, change its details, or add a comment. These actions affect your connected Linear workspace; they do not send a reply to the customer. ## Before you start Connect Linear in **Evelin AI → Integrations**. Open **Manage**, enable Evelin access and the permissions needed for your task, then select **Save changes**. Access remains limited to the teams authorized in Linear. For direct changes, the current assistant flow requires **Approve safe actions** and an explicit request from you. Despite the mode's name, authorized Linear writes can run in this mode. **Ask before changes** prevents automatic writes; do not assume every Linear operation has a separate confirmation card. Only submit a change request when you intend it to run. The examples below use placeholder issue keys, names, and labels. Replace them with values from your workspace. ## Find the right issue 1. Open the relevant conversation in **Threads** and open **Ask Evelin**. 2. Ask about an exact key, such as “Look up Linear issue PRO-123,” or request a keyword search, such as “Search Linear issues for checkout timeout.” 3. Check the issue key, title, and link before requesting a change. Keyword search matches issue titles or descriptions and returns a small set of recently updated matches. It is not a complete export or a search of all comments. Narrow the phrase if more matches exist. No results does not prove that no related issue exists outside the authorized teams or returned matches. ## Create an issue Give Evelin a clear creation request, the intended team, and the details to include. For example: > Create a Linear issue in team PRO titled “Checkout times out after payment.” Summarize the reproduction steps from this conversation. Set priority to High. You can also request an initial assignee and existing labels. Use an exact teammate name or email and exact label names when possible. If more than one team is available, name the intended team in your request. Evelin may ask you to clarify a team, assignee, or label instead of creating the issue. Reply with a new, explicit creation request containing the corrected details. A created issue includes a link back to the current Protodesk conversation. Its description can also include the conversation details used to prepare the issue. Review what you ask Evelin to include: this shares those details with people who can access the issue in Linear. After a confirmed creation, check the returned issue key and open its link. A drafted description or a suggested issue is not evidence that an issue was created. ## Update an existing issue Name the exact issue and the change. Supported requests include: | Task | Example request | | - | - | | Edit content | “Update PRO-123's title to ‘Checkout timeout after successful payment’.” | | Change status | “Move PRO-123 to In Progress.” | | Change priority | “Set PRO-123's priority to High.” | | Assign a teammate | “Assign PRO-123 to Ana Example.” | | Remove an assignee | “Unassign PRO-123.” | | Add an existing label | “Add the Bug label to PRO-123.” | | Remove an existing label | “Remove the Needs triage label from PRO-123.” | Status names must exist in the issue's team. Assignees must resolve to an eligible team member. Labels must already exist for that team or be available as shared workspace labels; this flow does not create labels. Adding or removing a label preserves unrelated labels. Each change needs its corresponding permission. For example, permission to edit issue content does not also grant permission to change its assignee. Creating an issue with initial details is separate from permission to update an existing issue. If a name matches more than one option, provide the exact name or teammate email requested by Evelin. Do not treat a clarification response as a completed change. ## Add a comment Use an explicit comment request: > Add a comment to PRO-123: “The customer reproduced this on the latest release. Reproduction steps are in the linked support conversation.” This posts to Linear, not to the customer conversation. Check the issue before posting sensitive customer details. Adding a comment does not send a Protodesk reply or automatically notify the customer through Protodesk. ## Continue with a follow-up After Evelin has verified one issue in the same private chat, a recent follow-up such as “Set that issue's priority to High” can use that issue as its target. If the chat discussed several issues, the reference is old, or you started another chat, use the exact key again. A previous request is not continuing permission to make unrelated changes. ## Check the outcome before repeating a request * **Confirmed change:** open the returned Linear link and check the result. * **Clarification or unavailable access:** resolve the named option, permission, or connection problem before requesting the action again. * **Unconfirmed or unknown result:** check Linear first. A timeout or missing confirmation can happen after Linear accepted the action. Repeating creation or a comment could produce a duplicate. Do not rely on a general Undo action to reverse Linear changes. If a correction is needed, inspect the current issue and make an explicit corrective request or edit it in Linear. Closing the chat, stopping an answer, or disconnecting Linear does not reverse a completed change. For project assignment, cycles, and linking an existing issue to the current conversation, see **Manage Linear projects, cycles, and conversation links**. For connection setup or permission changes, see **Connect Linear to Evelin** and **Manage Evelin's Linear permissions**. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.