> For the complete documentation index, see [llms.txt](https://docs.copia.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.copia.io/docs/git-based-source-control/additional-features/issues/references-and-links.md).

# References and Links

There are many ways that you can link your Issues within Copia, and also perform actionable references.  This makes it easy to cross reference your Issue to a PR or commit, and also automatically close or re-open your issue by performing a merge or commit.

## Linking

Every issue is assigned an ID, which is preceded by the `#` sign, after the title of the image.  This ID can be used to reference the issue in comments and descriptions within Copia. &#x20;

### Within a Repository

A reference to an Issue within the same repository can be created using the simple notation `#123`, where *123* is the ID of the Issue in the same repository. The references will be shown as link to the Issue.

### In another Repository

A reference to an Issue within another repository can be created by specifying both the Organization and the repository first, such as `orgname/reponame#123`, where *123* is the ID of the Issue. The references will be shown as link to the Issue.

## Actionable References

Copia also supports automatically closing and re-opening an Issue through the use of actionable references.  By using the Issue ID, along with certain keywords, the action will be taken.  For example, if you enter `closes #123` in the commit message, it will automatically close the corresponding Issue referenced. &#x20;

Below is a list of keywords that can be used.

* **Closing**: close, closes, closed, fix, fixes, fixed, resolve, resolves, resolved
* **Reopening**: reopen, reopens, reopened

In addition, there are a few conditions which must be met:

* The commenter must have permission to close or reopen the issue.
* The reference is inside a commit message.
* The reference is posted as part of the pull request description.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.copia.io/docs/git-based-source-control/additional-features/issues/references-and-links.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
