> ## 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.

## 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.