ProxmoxVE/.github/ISSUE_TEMPLATE/bug_report.yml

name: "🐞 Script Issue Report"
description: Report a specific issue with a script. For other inquiries, please use the Discussions section.
labels: ["bug"]
body:
  - type: markdown
    attributes:
      value: |
        ## ⚠️ **IMPORTANT - READ FIRST**

        **1. Reproduce the issue with verbose mode - this is mandatory.**
        Set `var_verbose=yes` (or *Advanced Settings → Verbose Mode*) and run the script again.
        Only a verbose log shows what actually failed - a bare `[ERROR] in line 23: exit code *` tells us nothing.
        **Reports without a verbose log will most likely be closed.**

        **2. Search before you post.**
        Check the [closed issues](https://github.com/community-scripts/ProxmoxVE/issues?q=is%3Aissue+is%3Aclosed) and the [Discussions](https://github.com/community-scripts/ProxmoxVE/discussions) (*Announcement* / *Guide*). If it is already known, comment there instead of opening a new issue.

        **3. Read the script.**
        Knowing what it does makes it much easier to describe the problem - and often to solve it yourself.

  - type: input
    id: guidelines
    attributes:
      label: ✅ Have you read and understood the above guidelines?
      placeholder: "yes"
    validations:
      required: true

  - type: dropdown
    id: verbose_run
    attributes:
      label: 🔎 Did you run the script with verbose mode enabled?
      description: "Required for debugging any script issue. A verbose log is mandatory."
      options:
        - "Yes, verbose mode was enabled and the output is included below"
        - "No (this issue will likely be closed automatically)"
    validations:
      required: true

  - type: input
    id: script_name
    attributes:
      label: 📜 What is the name of the script you are using?
      placeholder: "e.g., NextcloudPi, Zigbee2MQTT"
    validations:
      required: true

  - type: input
    id: script_command
    attributes:
      label: 📂 What was the exact command used to execute the script?
      placeholder: "e.g., bash -c \"$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/zigbee2mqtt.sh)\" or \"update\""
    validations:
      required: true

  - type: dropdown
    id: issue_phase
    attributes:
      label: 🕒 When does the issue occur?
      options:
        - "Initial creation / installation"
        - "Update of an existing container"
        - "While the application is running"
    validations:
      required: true

  - type: dropdown
    id: execution_context
    attributes:
      label: 🖱️ Where did you run the command?
      description: "The shell matters — the Proxmox web console starts without some environment variables that a normal login shell sets."
      options:
        - "Proxmox web UI → node → Shell"
        - "Proxmox web UI → LXC → Console"
        - "SSH into the Proxmox host"
        - "SSH into the container"
        - "pct enter from the host"
        - "Other / not listed"
    validations:
      required: true

  - type: checkboxes
    validations:
      required: true
    attributes:
      label: ⚙️ What settings are you using?
      options:
        - label: Default Settings
        - label: Advanced Settings

  - type: markdown
    attributes:
      value: "💡 **Tip:** If you are using Advanced Settings, please test with Default Settings before submitting an issue."

  - type: dropdown
    id: os_distribution
    attributes:
      label: 🖥️ Which Linux distribution is the container running?
      options:
        - Debian
        - Ubuntu
        - Alpine
        - Devuan
        - AlmaLinux
        - Rocky Linux
        - CentOS Stream
        - Fedora
        - openSUSE
        - openEuler
        - Gentoo
        - Other / not listed
    validations:
      required: true

  - type: input
    id: os_version
    attributes:
      label: 🔢 Which version of that distribution?
      description: "Run `cat /etc/os-release` inside the container if unsure."
      placeholder: "e.g. 13 (Debian), 24.04 (Ubuntu), 3.22 (Alpine)"
    validations:
      required: true

  - type: dropdown
    id: host_arm64
    attributes:
      label: 🧱 Is this Proxmox host running arm64?
      description: "Run `dpkg --print-architecture` on your Proxmox host if unsure."
      options:
        - "No"
        - "Yes"
    validations:
      required: true

  - type: dropdown
    id: pve_major
    attributes:
      label: 📈 Which Proxmox VE release are you on?
      options:
        - "Proxmox VE 9"
        - "Proxmox VE 8"
        - "Proxmox VE 7 or older (end of life)"
    validations:
      required: true

  - type: input
    id: pve_version
    attributes:
      label: 🔢 Exact Proxmox version and kernel
      description: "Both matter — several issues turned out to be kernel-specific."
      placeholder: "run pveversion in your PVE node console"
    validations:
      required: true

  - type: textarea
    id: issue_description
    attributes:
      label: 📝 Provide a clear and concise description of the issue.
    validations:
      required: true

  - type: textarea
    id: steps_to_reproduce
    attributes:
      label: 🔄 Steps to reproduce the issue.
      placeholder: "e.g., Step 1: ..., Step 2: ..."
    validations:
      required: true

  - type: textarea
    id: error_output
    attributes:
      label: ❌ Paste the full error output (if available).
      placeholder: "Include any relevant logs or error messages."
    validations:
      required: true

  - type: textarea
    id: additional_context
    attributes:
      label: 🖼️ Additional context (optional).
      placeholder: "Include screenshots, code blocks (use triple backticks ```), or any other relevant information."
    validations:
      required: false