# Administering issues

Learn about performing administrative tasks on issues in your repositories.

## Links

* [/triaging-an-issue-with-ai](/en/enterprise-server@3.17/triaging-an-issue-with-ai)

* [Pinning an issue to your repository](/en/enterprise-server@3.17/issues/tracking-your-work-with-issues/administering-issues/pinning-an-issue-to-your-repository)

  You can pin up to three important issues above the issues list in your repository.

* [Marking issues or pull requests as a duplicate](/en/enterprise-server@3.17/issues/tracking-your-work-with-issues/administering-issues/marking-issues-or-pull-requests-as-a-duplicate)

  Mark an issue or pull request as a duplicate to track similar issues or pull requests together and remove unnecessary burden for both maintainers and collaborators.

* [Transferring an issue to another repository](/en/enterprise-server@3.17/issues/tracking-your-work-with-issues/administering-issues/transferring-an-issue-to-another-repository)

  To move an issue to a better fitting repository, you can transfer open issues to other repositories.

* [Closing an issue](/en/enterprise-server@3.17/issues/tracking-your-work-with-issues/administering-issues/closing-an-issue)

  You can close an issue when bugs are fixed, feedback is acted on, or to show that work is not planned.

* [Deleting an issue](/en/enterprise-server@3.17/issues/tracking-your-work-with-issues/administering-issues/deleting-an-issue)

  People with admin permissions in a repository can permanently delete an issue from a repository.

* [/cloning-an-issue](/en/enterprise-server@3.17/cloning-an-issue)