Merge branch 'cw-2283' into 'dev'

GitHub issue templates [CW-2283]

See merge request epi2melabs/workflows/wf-transcriptomes!105

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,21 +1,17 @@
 name: Bug Report
 description: File a bug report
-title: "[Bug]: "
+labels: ["triage"]
-labels: ["bug", "triage"]
 body:
   - type: markdown
     attributes:
       value: |
         Thanks for taking the time to fill out this bug report!
-  - type: textarea
+
-    id: what-happened
+
+  - type: markdown
     attributes:
-      label: What happened?
+      value: |
-      description: Also tell us, what did you expect to happen?
+          # Background
-      placeholder: Tell us what you see!
-      value: "A bug happened!"
-    validations:
-      required: true
   - type: dropdown
     id: os
     attributes:
@@ -25,8 +21,22 @@ body:
         - Windows 10
         - Windows 11
         - macOS
-        - ubuntu 18.04
+        - Ubuntu 22.04
-        - ubuntu 20.04
+        - CentOS 7
+        - Other Linux (please specify below)
+    validations:
+      required: true
+  - type: input
+    id: other-os
+    attributes:
+      label: Other Linux
+      placeholder: e.g. Fedora 38
+  - type: input
+    id: version
+    attributes:
+      label: Workflow Version
+      description: This is most easily found in the workflow output log
+      placeholder: v1.2.3
     validations:
       required: true
   - type: dropdown
@@ -35,41 +45,80 @@ body:
       label: Workflow Execution
       description: Where are you running the workflow?
       options:
-        - EPI2ME Labs desktop application
+        - EPI2ME Desktop application
         - Command line
-        - EPI2ME
+        - EPI2ME cloud agent
         - Other (please describe)
     validations:
       required: true
+
+
+  - type: markdown
+    attributes:
+      value: |
+        # EPI2ME Desktop Application
+        If you are using the application please provide the following.
   - type: input
     id: labs-version
     attributes:
-      label: Workflow Execution - EPI2ME Labs Versions
+      label: EPI2ME Version
-      description: If you're running using EPI2ME Labs please provide the version and the environment version (Click the blue help icon bottom left and select ":bout")?
+      description: Available from the application settings page.
+      placeholder: v5.1.1
+    validations:
+      required: false
+
+
+  - type: markdown
+    attributes:
+      value: |
+        # Command-line execution
+        If you are using nextflow on a command-line, please provide the following.
+  - type: textarea
+    id: cli-command
+    attributes:
+      label: CLI command run
+      description: Please tell us the command you are running
+      placeholder: e.g. nextflow run epi2me-labs/wf-human-variations -profile standard --fastq my-reads/fastq
     validations:
       required: false
   - type: dropdown
     id: profile
     attributes:
       label: Workflow Execution - CLI Execution Profile
-      description: If you're using the CLI to run the workflow, what profile are you using?
+      description: Which execution profile are you using? If you are using a custom profile or nextflow configuration, please give details below.
       options:
-        - Docker
+        - standard (default)
-        - Singularity
+        - singularity
+        - custom
     validations:
       required: false
-  - type: input
+
-    id: version
+
+  - type: markdown
     attributes:
-      label: Workflow Version
+      value: |
-      description: What version of the workflow are you running?
+        # Report details
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Also tell us, what did you expect to happen?
+      placeholder: Tell us what you see!
     validations:
       required: true
   - type: textarea
     id: logs
     attributes:
       label: Relevant log output
-      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      description: For CLI execution please include the full output from running nextflow. For execution from the EPI2ME application please copy the contents of the "Workflow logs" panel from the "Logs" tab corresponding to your workflow instance. (This will be automatically formatted into code, so no need for backticks).
       render: shell
     validations:
       required: true
+  - type: textarea
+    id: activity-log
+    attributes:
+      label: Application activity log entry
+      description: For use with the EPI2ME application please see the Settings > View Activity Log page, and copy the contents of any items listed in red using the Copy to clipboard button.
+      render: shell
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,34 @@
+name: Feature request
+description: Suggest an idea for this project
+labels: ["feature request"]
+body:
+  
+  - type: textarea
+    id: question1
+    attributes:
+      label: Is your feature related to a problem?
+      placeholder: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+    validations:
+      required: true
+  - type: textarea
+    id: question2
+    attributes:
+      label: Describe the solution you'd like
+      placeholder: A clear and concise description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    id: question3
+    attributes:
+      label: Describe alternatives you've considered
+      placeholder: A clear and concise description of any alternative solutions or features you've considered.
+    validations:
+      required: true
+  - type: textarea
+    id: question4
+    attributes:
+      label: Additional context
+      placeholder: Add any other context about the feature request here.
+    validations:
+      required: false
+

.github/ISSUE_TEMPLATE/question.yml

@@ -0,0 +1,17 @@
+name: Question
+description: Ask a generic question about this project unrelated to features or bugs.
+labels: ["question"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Please reserve this form for issues not related to bugs or feature requests. If our developers deem your questions to be related to bugs or features you will be asked to fill in the appropriate form.
+  - type: textarea
+    id: question1
+    attributes:
+      label: Ask away!
+      placeholder: |
+          Bad question: How do I use this workflow in my HPC cluster?
+          Good question: My HPC cluster uses a GridEngine scheduler. Can you point me to documentation for how to use your workflows to efficiently submit jobs to my cluster?
+    validations:
+      required: true

CHANGELOG.md

@@ -4,10 +4,15 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [unreleased]
+### Changed
+- GitHub issue templates
+
 ## [v0.1.13]
 ### Added
 - Handling for GFF3 reference_annotation file type.
 - Warning for the `--transcriptome_source` denovo pipeline option.
+
 ### Changed
 - Enum choices are enumerated in the `--help` output
 - Enum choices are enumerated as part of the error message when a user has selected an invalid choice