From fb2149f0c8e8b51e001336ed19e5b44b7860aecb Mon Sep 17 00:00:00 2001 From: Markus Unterwaditzer Date: Fri, 6 Jun 2025 19:50:48 +0200 Subject: [PATCH] Loosen up issue templates A lot of the bug report we receive are about the web UI or the installer failing, and there things like capture date just don't matter. We could create separate templates for these types of bugs, but I'd think it's probably better to just have one textbox with a few "reminder" questions that are all optional. Feature request template I think doesn't have this issue. Also allow the creation of blank issues, because some issues are more related to CI or devenv and don't neatly fit in any category. Let's just hope nobody abuses that? --- .github/ISSUE_TEMPLATE/bug.yaml | 62 +++++------------------------ .github/ISSUE_TEMPLATE/config.yml | 2 +- .github/ISSUE_TEMPLATE/feature.yaml | 1 - 3 files changed, 12 insertions(+), 53 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug.yaml b/.github/ISSUE_TEMPLATE/bug.yaml index 97f9373..ea43089 100644 --- a/.github/ISSUE_TEMPLATE/bug.yaml +++ b/.github/ISSUE_TEMPLATE/bug.yaml @@ -1,59 +1,19 @@ name: Bug Report description: File a bug report. -title: "[Bug]: " +labels: ["bug"] body: - - type: markdown - attributes: - value: | - Thanks for taking the time to fill out this bug report! - - type: input - attributes: - label: Rayhunter Version - description: | - Which version did you install? - placeholder: "v0.2.6" - - type: input - attributes: - label: Capture Date - description: | - YYYY-MM-DD - placeholder: "2025-05-01" - validations: - required: true - - type: input - attributes: - label: Capture Location - description: | - (If comfortable disclosing) What region or country were you in? - placeholder: Washington State - - type: input - attributes: - label: Device and Model - description: | - Device you installed Rayhunter on to. - placeholder: Orbic RC400L - validations: - required: true - type: textarea - id: what-happened attributes: - label: What happened? + label: Bug Report Details description: | - What steps did you take to get to your issue? - placeholder: "Tell us what you see!" + Please provide the following information, if applicable: + placeholder: | + • **Rayhunter Version**: (e.g., v0.2.6) + • **Capture Date**: (YYYY-MM-DD, e.g., 2025-05-01) + • **Capture Location**: (If comfortable disclosing, what region or country were you in? e.g., Washington State) + • **Device and Model**: (Device you installed Rayhunter on, e.g., Orbic RC400L) + • **What happened?**: (What steps did you take to get to your issue? Tell us what you see!) + • **Expected behavior**: (Rayhunter's behavior differed from what I expected because...) + • **Relevant log output**: (Rayhunter data captures - QMDL and PCAP logs - or error codes) validations: required: true - - type: textarea - id: expected - attributes: - label: Expected behavior - description: Rayhunter's behavior differed from what I expected because. - placeholder: "What was expected?" - validations: - required: true - - type: textarea - id: logs - attributes: - label: Relevant log output - description: Rayhunter data captures (QMDL and PCAP logs) or error codes - render: shell diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index 35b33e2..fdfe3da 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -1,4 +1,4 @@ -blank_issues_enabled: false +blank_issues_enabled: true contact_links: - name: Rayhunter Mattermost url: https://opensource.eff.org/signup_user_complete/?id=6iqur37ucfrctfswrs14iscobw&md=link&sbr=su diff --git a/.github/ISSUE_TEMPLATE/feature.yaml b/.github/ISSUE_TEMPLATE/feature.yaml index 1e2a35a..fd5871e 100644 --- a/.github/ISSUE_TEMPLATE/feature.yaml +++ b/.github/ISSUE_TEMPLATE/feature.yaml @@ -1,6 +1,5 @@ name: Feature Request description: Suggest a new feature or improvement to Rayhunter -title: "[Feature Request]: " labels: ["enhancement"] body: - type: textarea