> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Links

> Connect Ravenna tickets to external resources like GitHub or Jira for context and bi-directional sync with integrated ticketing systems.

Connect tickets to external resources like GitHub issues, design documents, or integrated ticketing systems. Add manual links for context or let integrations create them automatically for bi-directional sync.

<View title="Human" icon="user">
  ***

  ## What are ticket links?

  Ticket links connect your Ravenna tickets to external resources and systems. Add manual links for context or let integrations create links automatically for bi-directional sync with tools like Slack, Jira, and Linear.

  ***

  ## Add ticket links

  ### Manual links

  Add links to external resources directly from any ticket:

  <Steps>
    <Step title="Open ticket">
      Navigate to the ticket you want to add a link to.
    </Step>

    <Step title="Access links section">
      Find the links section in the ticket details.
    </Step>

    <Step title="Add new link">
      Click **Add Link** or the plus button.
    </Step>

    <Step title="Enter URL">
      Enter the external URL you want to link to. Ravenna automatically fetches the page title to use as the link name.
    </Step>

    <Step title="Review or customize name">
      The name field auto-populates with the page title. You can edit it to customize the link name if desired.
    </Step>

    <Step title="Save link">
      Click **Save** to create the link.
    </Step>
  </Steps>

  <Info>
    When you paste a URL, Ravenna automatically fetches the page title to populate the link name. For Ravenna ticket URLs, it uses the ticket title. For external URLs, it extracts the page title from the site's metadata. You can always edit the auto-generated name before saving.
  </Info>

  ### Integration links

  Some links are created automatically through system integrations:

  <AccordionGroup>
    <Accordion title="Slack" icon="slack" defaultOpen>
      * Automatically creates links when tickets are created from Slack messages
      * Provides direct access to the original Slack conversation
    </Accordion>

    <Accordion title="Jira" icon={<img src="/icons/jira.svg" className="w-4 h-4" />}>
      * Creates links when tickets are synchronized with Jira issues
      * Enables bi-directional updates between Ravenna and Jira
      * Maintains real-time sync through webhooks
    </Accordion>

    <Accordion title="Linear" icon={<img src="/icons/linear.svg" className="w-4 h-4" />}>
      * Automatically links when Linear issues are created
      * Provides direct access to Linear workspace issues
      * Supports workflow automation between systems
    </Accordion>
  </AccordionGroup>

  ***

  ## Manage ticket links

  ### Edit links

  <Steps>
    <Step title="Locate link">
      Find the link you want to edit in the ticket's links section.
    </Step>

    <Step title="Open edit options">
      Click the edit button or dropdown menu for the link.
    </Step>

    <Step title="Update details">
      Modify the name or URL as needed.
    </Step>

    <Step title="Save changes">
      Click **Save** to update the link.
    </Step>
  </Steps>

  ### Delete links

  <Steps>
    <Step title="Select link">
      Find the link you want to remove in the ticket's links section.
    </Step>

    <Step title="Delete action">
      Click the delete button or select **Delete** from the dropdown menu.
    </Step>

    <Step title="Confirm deletion">
      Confirm the deletion when prompted. This action cannot be undone.
    </Step>
  </Steps>

  ***

  ## Use ticket links

  <AccordionGroup>
    <Accordion title="Quick access" icon="external-link" defaultOpen>
      Click any link to open the external resource in a new tab. Links display with favicons and domain information for easy identification.
    </Accordion>

    <Accordion title="Context and reference" icon="book-open">
      Use links to provide additional context for tickets, reference related documentation, pull requests, or external issues, and share resources with team members.
    </Accordion>

    <Accordion title="Integration sync" icon="refresh-cw">
      Integration links maintain bi-directional sync with external systems, keeping ticket information consistent across platforms.
    </Accordion>
  </AccordionGroup>
</View>

<View title="Agent" icon="bot">
  ## Mental model

  Ticket links are URL references attached to a ticket. They come in two forms:

  * **Manual links**: User-added URLs to any external resource (documentation, pull requests, design files, etc.). These are display-only references with no sync behavior.
  * **Integration links**: System-created links from integrations (Slack, Jira, Linear). These can support bi-directional sync, meaning changes in one system propagate to the other.

  Links are distinct from ticket relations. Links point to external resources (URLs). Ticket relations connect Ravenna tickets to each other (parent/child, related).

  ***

  ## Links vs. relations vs. sharing

  | Mechanism     | Connects                          | Sync behavior                                               |
  | ------------- | --------------------------------- | ----------------------------------------------------------- |
  | **Links**     | Ticket to external URL            | Manual links: none. Integration links: bi-directional sync. |
  | **Relations** | Ticket to ticket (within Ravenna) | Parent/child hierarchy, related tickets                     |
  | **Sharing**   | Ticket visibility across channels | Same ticket appears in multiple channels                    |

  Use links when referencing external systems. Use relations when connecting Ravenna tickets. Use sharing when multiple teams need to see the same ticket.

  ***

  ## Integration link behavior

  **Slack:** When a ticket is created from a Slack message, a link to the original Slack thread is automatically attached. This is read-only context, not sync.

  **Jira / Linear (ticket replication):** When ticket replication is enabled, integration links are created automatically and maintain bi-directional sync. Status changes, comments, and updates propagate between systems. These links are managed by the integration, not by users.

  ***

  ## Constraints and gotchas

  * Manual links are simple URL references. They do not sync, update, or validate that the target resource still exists.
  * Integration links are system-managed. Deleting an integration link can break replication sync. Avoid manually deleting integration-created links.
  * Links have a name and URL. When adding a link, the system auto-fetches the page title, but this can be overridden.
</View>