diff --git a/.gitea/ISSUE_TEMPLATE/bug-report.md b/.gitea/ISSUE_TEMPLATE/bug-report.md
deleted file mode 100644
index d334ea6e63..0000000000
--- a/.gitea/ISSUE_TEMPLATE/bug-report.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-name: "Bug Report"
-about: "Found something you weren't expecting? Report it here!"
-title: "[BUG] "
----
-<!--
-NOTE: If your issue is a security concern, please email security@forgejo.org (GPG: A4676E79) instead of opening a public issue.
-
-1. Please speak English, as this is the language all maintainers can
-   speak and write.
-
-2. Please ask questions or troubleshoot configuration/deploy problems
-   in our Matrix space (https://matrix.to/#/#forgejo:matrix.org).
-
-3. Please make sure you are using the latest release of Forgejo and
-   take a moment to check that your issue hasn't been reported before.
-
-4. Please give all relevant information below for bug reports, because
-   incomplete details will be handled as an invalid report.
-
-5. If you are using a proxy or a CDN (e.g. CloudFlare) in front of
-   Forgejo, please disable the proxy/CDN fully and connect to Forgejo
-   directly to confirm the issue still persists without those services.
--->
-
-- Can you reproduce the problem on [Forgejo Next](https://next.forgejo.org/)?
-- Forgejo version (or commit ref):
-- Git version:
-- Operating system:
-- Database (use `[x]`):
-  - [ ] PostgreSQL
-  - [ ] MySQL
-  - [ ] MSSQL
-  - [ ] SQLite
-- How are you running Forgejo?
-<!--
-Please include information on whether you built Forgejo yourself, used one of our downloads, or are using some other package.
-Please also tell us how you are running Forgejo, e.g. if it is being run from docker, a command-line, systemd etc.
-If you are using a package or systemd tell us what distribution you are using.
--->
-
-## Description
-<!-- Please describe the issue you are having as clearly and succinctly as possible. -->
-
-## Reproducing
-<!-- Please explain how to cause the problem to occur on demand if possible. -->
-
-## Logs
-<!--
-It is really important to provide pertinent logs. We need DEBUG level logs.
-Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems
-In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of `app.ini`.
-Please copy and paste your logs here, with any sensitive information (e.g. API keys) removed/hidden.
--->
-
-## Screenshots
-<!-- If this issue involves the Web Interface, please provide one or more screenshots -->
diff --git a/.gitea/ISSUE_TEMPLATE/feature-request.md b/.gitea/ISSUE_TEMPLATE/feature-request.md
deleted file mode 100644
index 3708f2514e..0000000000
--- a/.gitea/ISSUE_TEMPLATE/feature-request.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-name: "Feature Request"
-about: "Got an idea for a feature that Forgejo doesn't have yet? Submit it here!"
-title: "[FEAT] "
----
-<!--
-1. Please speak English, as this is the language all maintainers can
-   speak and write.
-
-2. Please ask questions or troubleshoot configuration/deploy problems
-   in our Matrix space (https://matrix.to/#/#forgejo:matrix.org).
-
-3. Please make sure you are using the latest release of Forgejo and
-   take a moment to check that your feature hasn't already been suggested.
--->
-
-## Needs and benefits
-<!-- Please describe the needs this feature intends to address and the benefits it brings. -->
-
-## Feature Description
-<!-- Please describe the feature you would like to see added as clearly and succinctly as possible. -->
-
-## Screenshots
-<!-- If you can, provide screenshots of an implementation on another site, e.g. GitHub. -->
diff --git a/.gitea/issue_template/bug-report-ui.yaml b/.gitea/issue_template/bug-report-ui.yaml
new file mode 100644
index 0000000000..4d80198399
--- /dev/null
+++ b/.gitea/issue_template/bug-report-ui.yaml
@@ -0,0 +1,63 @@
+name: 🦋 Bug Report (web interface / frontend)
+description: Something doesn't look quite as it should?  Report it here!
+title: "[BUG] "
+labels: ["bug", "forgejo/ui"]
+body:
+- type: markdown
+  attributes:
+    value: |
+      **NOTE: If your issue is a security concern, please email <security@forgejo.org> (GPG: `A4676E79`) instead of opening a public issue.**
+- type: markdown
+  attributes:
+    value: |
+      - Please speak English, as this is the language all maintainers can speak and write.
+      - Be as clear and concise as possible. A very verbose report is harder to interpret in a concrete way.
+      - Be civil, and follow the [Forgejo Code of Conduct](https://codeberg.org/forgejo/code-of-conduct).
+      - Please make sure you are using the latest release of Forgejo and take a moment to [check that your issue hasn't been reported before](https://codeberg.org/forgejo/forgejo/issues?q=&type=all&labels=78137).
+      - Please give all relevant information below for bug reports, as incomplete details may result in the issue not being considered.
+- type: textarea
+  id: description
+  attributes:
+    label: Description
+    description: |
+      Please provide a description of your issue here, with a URL if you were able to reproduce the issue (see below).
+      If you think this is a JavaScript error, show us the JavaScript console.
+      If the error appears to relate to Forgejo the server, please also give us `DEBUG` level logs. (See https://forgejo.org/docs/latest/admin/logging-documentation/)
+- type: textarea
+  id: screenshots
+  attributes:
+    label: Screenshots
+    description: Please provide at least one screenshot showing the issue.
+  validations:
+    required: true
+- type: input
+  id: forgejo-ver
+  attributes:
+    label: Forgejo Version
+    description: Forgejo version (or commit reference) your instance is running
+  validations:
+    required: true
+- type: dropdown
+  id: can-reproduce
+  attributes:
+    label: Can you reproduce the bug on Forgejo Next?
+    description: |
+      Please try reproducing your issue at [Forgejo Next](https://next.forgejo.org).
+      If you can reproduce it, please provide a URL in the Description field.
+    options:
+    - "Yes"
+    - "No"
+  validations:
+    required: true
+- type: input
+  id: browser-ver
+  attributes:
+    label: Browser Version
+    description: The browser and version that you are using to access Forgejo
+  validations:
+    required: true
+- type: input
+  id: os-ver
+  attributes:
+    label: Operating System
+    description: The operating system you are using to access Forgejo
diff --git a/.gitea/issue_template/bug-report.yaml b/.gitea/issue_template/bug-report.yaml
new file mode 100644
index 0000000000..ce67378175
--- /dev/null
+++ b/.gitea/issue_template/bug-report.yaml
@@ -0,0 +1,90 @@
+name: 🐛 Bug Report (server / backend)
+description: Found something you weren't expecting? Report it here!
+title: "[BUG] "
+labels: bug
+body:
+- type: markdown
+  attributes:
+    value: |
+      **NOTE: If your issue is a security concern, please email <security@forgejo.org> (GPG: `A4676E79`) instead of opening a public issue.**
+- type: markdown
+  attributes:
+    value: |
+      - Please speak English, as this is the language all maintainers can speak and write.
+      - Be as clear and concise as possible. A very verbose report is harder to interpret in a concrete way.
+      - Be civil, and follow the [Forgejo Code of Conduct](https://codeberg.org/forgejo/code-of-conduct).
+      - Please make sure you are using the latest release of Forgejo and take a moment to [check that your issue hasn't been reported before](https://codeberg.org/forgejo/forgejo/issues?q=&type=all&labels=78137).
+      - Please give all relevant information below for bug reports, as incomplete details may result in the issue not being considered.
+- type: textarea
+  id: description
+  attributes:
+    label: Description
+    description: |
+      Please provide a description of your issue here, with a URL if you were able to reproduce the issue (see below).
+  validations:
+    required: true
+- type: input
+  id: forgejo-ver
+  attributes:
+    label: Forgejo Version
+    description: Forgejo version (or commit reference) of your instance
+  validations:
+    required: true
+- type: dropdown
+  id: can-reproduce
+  attributes:
+    label: Can you reproduce the bug on Forgejo Next?
+    description: |
+      Please try reproducing your issue at [Forgejo Next](https://next.forgejo.org).
+      If you can reproduce it, please provide a URL in the Description field.
+    options:
+    - "Yes"
+    - "No"
+  validations:
+    required: true
+- type: textarea
+  id: logs
+  attributes:
+    label: Logs
+    description: |
+      It's really important to provide pertinent logs. You must give us `DEBUG` level logs.
+      Please read https://forgejo.org/docs/latest/admin/logging-documentation/.
+      In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of `app.ini`.
+
+      Please copy and paste your logs here, with any sensitive information (e.g. API keys) removed/hidden.
+      You can wrap your logs in `<details>...</details>` tags so it doesn't take up too much space in the issue.
+- type: textarea
+  id: screenshots
+  attributes:
+    label: Screenshots
+    description: If this issue involves the Web Interface, please provide one or more screenshots
+- type: input
+  id: git-ver
+  attributes:
+    label: Git Version
+    description: The version of git running on the server
+- type: input
+  id: os-ver
+  attributes:
+    label: Operating System
+    description: The operating system you are using to run Forgejo
+- type: textarea
+  id: run-info
+  attributes:
+    label: How are you running Forgejo?
+    description: |
+      Please include information on whether you built Forgejo yourself, used one of our downloads, or are using some other package.
+      Please also tell us how you are running Forgejo, e.g. if it is being run from docker, a command-line, systemd etc.
+      If you are using a package or systemd tell us what distribution you are using.
+  validations:
+    required: true
+- type: dropdown
+  id: database
+  attributes:
+    label: Database
+    description: What database system are you running?
+    options:
+    - SQLite
+    - PostgreSQL
+    - MySQL
+    - MSSQL
diff --git a/.gitea/issue_template/config.yml b/.gitea/issue_template/config.yml
new file mode 100644
index 0000000000..3a8cdb1ad1
--- /dev/null
+++ b/.gitea/issue_template/config.yml
@@ -0,0 +1,17 @@
+blank_issues_enabled: false
+contact_links:
+  - name: 🔓 Security Reports
+    url: mailto:security@forgejo.org
+    about: "Please email <security@forgejo.org> (GPG: `A4676E79`) instead of opening a public issue."
+  - name: 💬 Matrix Chat Room
+    url: https://matrix.to/#/#forgejo-chat:matrix.org
+    about: Please ask questions and discuss configuration or deployment problems here.
+  - name: 💬 Matrix Space
+    url: https://matrix.to/#/#forgejo:matrix.org
+    about: A collection of Matrix rooms relating to Forgejo in addition to the main chat room.
+  - name: 📚 Documentation
+    url: https://forgejo.org/docs/latest/
+    about: Documentation about Forgejo.
+  - name: ❓ Frequently Asked Questions
+    url: https://forgejo.org/faq/
+    about: Please check if your question is mentioned here.
diff --git a/.gitea/issue_template/feature-request.yaml b/.gitea/issue_template/feature-request.yaml
new file mode 100644
index 0000000000..4b10bea145
--- /dev/null
+++ b/.gitea/issue_template/feature-request.yaml
@@ -0,0 +1,31 @@
+name: 💡 Feature Request
+description: Got an idea for a feature that Forgejo doesn't have yet? Suggest it here!
+title: "[FEAT] "
+labels: ["enhancement/feature"]
+body:
+- type: markdown
+  attributes:
+    value: |
+      - Please speak English, as this is the language all maintainers can speak and write.
+      - Be as clear and concise as possible. A very verbose request is harder to interpret in a concrete way.
+      - Be civil, and follow the [Forgejo Code of Conduct](https://codeberg.org/forgejo/code-of-conduct).
+      - Please make sure you are using the latest release of Forgejo and take a moment to [check that your feature hasn't already been suggested](https://codeberg.org/forgejo/forgejo/issues?q=&type=all&labels=78139).
+- type: textarea
+  id: needs-benefits
+  attributes:
+    label: Needs and benefits
+    description: As concisely as possible, describe the benefits your feature request will provide or the problems it will try to solve.
+  validations:
+    required: true
+- type: textarea
+  id: description
+  attributes:
+    label: Feature Description
+    description: As concisely as possible, describe the feature you would like to see added or the changes you would like to see made to Forgejo.
+  validations:
+    required: true
+- type: textarea
+  id: screenshots
+  attributes:
+    label: Screenshots
+    description: If you can, provide screenshots of an implementation on another site, e.g. GitHub.