diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md deleted file mode 100644 index bc4b25ceb..000000000 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -name: Bug -about: Tell us about something that seems broken -title: '' -labels: ['defect', 'needs triage'] -projects: ['wordplaydev/7'] -assignees: '' ---- - -## Expected behavior - -A clear and concise description of what you expected to happen. - -## Actual behavior - -Provide detailed steps that consistently reproduce the behavior, including any example code. If you can, make the steps as minimal as possible, finding the smallest possible set of steps that still produce the unexpected behavior. - -1. Go to '...' -2. Click on '....' -3. Scroll down to '....' -4. See error - -## Screenshots - -If applicable, add screenshots to help explain your problem. - -## Environment - -What platform, OS, browser, and version are you using? Please be exact with version numbers, as different versions can result in a defect happening or not. Don't skip these; cross-browser issues are a common cause of problems. - -Desktop - -- OS + version: [e.g. mac OS 14.0] -- Browser + version [e.g. Chrome 118] - -Smartphone - -- Device: [e.g. iPhone6] -- OS + version: [e.g. iOS 17.1] -- Browser + version [e.g. Safari] - -If you're not reporting an issue on the production site, also describe the environment you are running in (vite dev server, vite build, whether the Firebase emulator is running, whether you're authenticated using the emulator and how.) - -## Design specification - -_If this defect requires some redesign, include a design proposal here (and if you don't have one, add the `needs design` label, and you can just write TBD here). Design proposals should describe, in precise detail \_what_ the proposed design is, but not necessarily how it might be built. Note that the design proposal for a defect should align with the expected behavior you described above. Once the design is approved, we will add the `buildable` tag is added.\_ diff --git a/.github/ISSUE_TEMPLATE/defect.yml b/.github/ISSUE_TEMPLATE/defect.yml new file mode 100644 index 000000000..2494eed7c --- /dev/null +++ b/.github/ISSUE_TEMPLATE/defect.yml @@ -0,0 +1,47 @@ +name: Defect +description: Report something not working as intended. +labels: ['defect', 'triage'] +projects: ['wordplaydev/7'] +body: + - type: markdown + attributes: + value: | + Thanks for taking the time to fill out this defect report! + - type: textarea + id: what-happened + attributes: + label: What happened? + placeholder: What happened? + description: | + Provide list of steps that consistently reproduce the behavior, including any example code. + 1. In this environment... + 1. With this config... + 1. Run '...' + 1. See error... + Make the steps as minimal as possible, finding the smallest possible set of steps that still produce the unexpected behavior. What is the defect and what did you expect to happen instead? + validations: + required: true + - type: textarea + attributes: + label: Anything else? + description: | + Any links, references, or other context that would help, or guesses about what might be causing it? You can attach images or log files by clicking this area to highlight it and then dragging files in. + - type: dropdown + id: browsers + attributes: + label: What browsers are you seeing the problem on? + multiple: true + options: + - Firefox + - Chrome + - Safari + - Microsoft Edge + - type: dropdown + id: os + attributes: + label: What operating system are you using? + multiple: true + options: + - Windows + - macOS + - Linux \ No newline at end of file diff --git a/.github/ISSUE_TEMPLATE/enhancement.yml b/.github/ISSUE_TEMPLATE/enhancement.yml new file mode 100644 index 000000000..9f27fc67b --- /dev/null +++ b/.github/ISSUE_TEMPLATE/enhancement.yml @@ -0,0 +1,25 @@ +name: Enhancement +description: Share an idea for improving Wordplay. +labels: ['enhancement', 'triage'] +projects: ['wordplaydev/7'] +body: +- type: markdown + attributes: + value: | + Thanks for sharing your idea! +- type: textarea + id: problem + attributes: + label: What are you trying to do that you can't? + description: In as much detail as possible, describe the task or problem you want to solve that Adminima doesn't currently support. + placeholder: Problem + validations: + required: true +- type: textarea + id: idea + attributes: + label: What is your idea? + description: If you have an idea for how to change Wordplay to support your task, share it here. It's okay if you don't. + placeholder: Ideas + validations: + required: true diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md deleted file mode 100644 index 03fe12089..000000000 --- a/.github/ISSUE_TEMPLATE/feature_request.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -name: Enhancement -about: Suggest new or improved features, functionalty, or content -title: '' -labels: ['enhancement', 'needs design', 'needs triage'] -projects: ['wordplaydev/7'] -assignees: '' ---- - -## What's the problem? - -- What is the task, goal, need, or opportunity this request would address? -- What is the context or scenario in which they would experience it? -- Who is the group of people who would be in this situation? -- What is it about the current design that makes the need above hard to satisfy? - -If what you're describing above is broken functionality, including usability, accessibility, localization problems, report those as defects, as they are things to be fixed, not added. - -## What's the design idea? - -What do you propose to change or add to address the problem above? Describe some functionality, a design concept, a redesign, or alternative designs that might address the problem. Provide as much detail about the idea as you currently have, but no need to provide an exact design specification if you don't have one. (That goes below). - -## Design specification - -_Reporters can leave this blank. Designers should write a detailed, precise description of what is to be built. If images are necessary to convey this precisely, make sure to include image descriptions, so everyone can see what is in the image. Do not link to external documents; everything should be embedded here. Once the design is approved, we will remove the `needs design` tag and replace it with the `buildable` tag, signalling that it can be built._ diff --git a/.github/ISSUE_TEMPLATE/maintenance.md b/.github/ISSUE_TEMPLATE/maintenance.md deleted file mode 100644 index 0f0ab39dc..000000000 --- a/.github/ISSUE_TEMPLATE/maintenance.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -name: Maintenance -about: Suggest an improvement to project maintenance -title: '' -labels: ['maintainability', 'needs triage'] -projects: ['wordplaydev/7'] -assignees: '' ---- - -## What's the maintenance need? - -Is there developer experience we need to improve, some technical debt that we should pay off, or some infrastructure missing? - -## Who benefits? - -Is this something you think only you would benefit from? Are there others that would benefit? Are there others that might be harmed by supporting this?