.gitea/ISSUE_TEMPLATE/bug_report.yaml

@@ -58,7 +58,7 @@ body:
       description: |
         Provide relevant logs, error messages, or screenshots.
         For logs, please use a pastebin and share the URL.
-        **Remember to remove any sensitive information (API keys, passwords, etc.).**[reference:13]
+        **Remember to remove any sensitive information (API keys, passwords, etc.).**
       placeholder: "Paste logs here or provide a Gist URL..."
     validations:
       required: false
@@ -70,33 +70,6 @@ body:
         ## 🖥️ Environment Details
         Please fill out the relevant information below.
 
-  - type: input
-    id: version
-    attributes:
-      label: "📦 Audio Splitter Version"
-      description: "The version you are using (or commit reference)"
-      placeholder: "e.g., v1.21.7"
-    validations:
-      required: true
-
-  - type: input
-    id: os
-    attributes:
-      label: "💻 Operating System"
-      description: "Your OS and version"
-      placeholder: "e.g., Ubuntu 22.04, macOS Sonoma 14.5, Windows"
-    validations:
-      required: true
-
-  - type: input
-    id: browser
-    attributes:
-      label: "🌍 Browser (if applicable)"
-      description: "Browser name and version"
-      placeholder: "e.g., Chrome 120, Firefox 121, Safari 17"
-    validations:
-      required: false
-
   - type: textarea
     id: additional
     attributes:
@@ -104,7 +77,7 @@ body:
       description: "Any other information that might be relevant"
       placeholder: |
         - Database type and version (e.g., PostgreSQL 15, SQLite)
-        - Reverse proxy/CDN in use (e.g., Nginx, Cloudflare)[reference:15]
+        - Reverse proxy/CDN in use (e.g., Nginx, Cloudflare)
         - Any custom configuration
         - Related issues or PRs
     validations:
@@ -118,8 +91,6 @@ body:
       options:
         - label: "I have searched for existing issues (open and closed) that report the same problem"
           required: true
-        - label: "I am using the latest stable release of Audio Splitter"
-          required: true
         - label: "I have provided clear steps to reproduce the issue"
           required: true
         - label: "I have included relevant logs or error messages (with sensitive info removed)"

.gitea/ISSUE_TEMPLATE/feature_request.yaml

@@ -9,7 +9,7 @@ body:
         ## ⚠️ Before You Begin
         Please ensure you have:
         - [ ] Searched existing issues (open and closed) to avoid duplicates
-        - [ ] Reviewed the [project documentation](https://git.vmn.su/max/audio_splitter/wiki) for existing functionality
+        - [ ] Reviewed the [project documentation](https://git.vmn.su/max/vmn-ansible/wiki) for existing functionality
         - [ ] Confirmed this is a feature request, not a bug or configuration question
 
 
@@ -48,17 +48,6 @@ body:
     validations:
       required: false
 
-  - type: textarea
-    id: usecase
-    attributes:
-      label: "👤 Use Case / Persona"
-      description: "Who benefits from this feature and in what context?"
-      placeholder: |
-        As a [type of user], I want to [do something] so that [I achieve some benefit].
-        Example: "As a project maintainer, I want to bulk-close issues by label so that I can clean up stale tickets faster."
-    validations:
-      required: false
-
   - type: textarea
     id: screenshots
     attributes:

.gitea/ISSUE_TEMPLATE/refactor.yaml

@@ -9,7 +9,7 @@ body:
         ## ⚠️ Before You Begin
         Please ensure you have:
         - [ ] Searched existing issues (open and closed) to avoid duplicates
-        - [ ] Reviewed the [project documentation](https://git.vmn.su/max/audio_splitter/wiki) for architecture guidelines
+        - [ ] Reviewed the [project documentation](https://git.vmn.su/max/vmn-ansible/wiki) for architecture guidelines
         - [ ] Confirmed this is a refactor (code restructuring with NO behavior change), not a bug fix or new feature
 
 
@@ -105,19 +105,6 @@ body:
     validations:
       required: false
 
-  - type: textarea
-    id: testing
-    attributes:
-      label: "🧪 Testing Strategy"
-      description: "How will you ensure the refactor doesn't break existing functionality?"
-      placeholder: |
-        - Existing test suite must pass
-        - Add regression tests before refactoring
-        - Run benchmarks to ensure no performance regression
-        - Manual testing of critical paths
-    validations:
-      required: true
-
   - type: textarea
     id: alternatives
     attributes:
@@ -153,8 +140,6 @@ body:
         - label: "I have clearly explained the problem this refactor solves"
           required: true
         - label: "I have described the scope of the refactor (specific files/modules)"
-          required: true
+          required: false
         - label: "I have identified what must NOT change (APIs, behavior, backward compatibility)"
-          required: true
-        - label: "I have described how the refactor will be tested"
-          required: true
+          required: false