Update GitHub issue templates (#14745)

jonthysell · web-flow · commit 5fc1c3121e20 · 2025-06-10T00:44:30.000Z
## Description

This PR cleans up our existing GitHub issue templates to remove prompts for unnecessary information while also making some prompts required and harder to ignore, to reduce the amount of time we send back issues for more information.

This PR also adds a new "Missing API" template to capture when expected React Native APIs aren't present on Windows.

### Type of Change
- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)

### Why
See above.

### What
See above.

## Screenshots
N/A

## Testing
N/A

## Changelog
Should this change be included in the release notes: _no_
diff --git a/.github/ISSUE_TEMPLATE/bug-report.yaml b/.github/ISSUE_TEMPLATE/bug-report.yaml
@@ -2,17 +2,27 @@ name: Bug report
 description: File a bug report
 title: Describe the problem
 labels: [bug]
+type: 'Bug'
 body:
   - type: markdown
     attributes:
       value: |
+        This form is for reporting bugs found in React Native for Windows.
+        
+        If the issue is that an existing React Native API is simply missing in React Native for Windows, please use the [this form](https://github.com/microsoft/react-native-windows/issues/new?template=missing-api.yaml) instead.
+
+        If you just have a question, please post on [Discussions](https://github.com/microsoft/react-native-windows/discussions) instead.
+
         Your issue will be triaged by the RNW team according to [this process](https://github.com/microsoft/react-native-windows/wiki/Triage-Process).
   - type: textarea
     validations:
       required: true
     attributes:
       label: Problem Description
-      description: Please enter a description of the issue. If you just have a question, please post on [Discussions](https://github.com/microsoft/react-native-windows/discussions).
+      description: |
+        Please enter a description of the issue and any output and/or error logging.
+        
+        If you're seeing a failure when using a RNW CLI command (i.e. `run-windows`, `autolink-windows`, `codegen-windows`) please try again with `--logging` and provide that output.
     id: description
   - type: textarea
     validations:
@@ -35,54 +45,63 @@ body:
     attributes:
       label: CLI version
       description: |
-        Run the command `npx @react-native-community/cli --version` in your terminal and copy the results here
-      value: "npx @react-native-community/cli -v"
+        Run the command `npx @react-native-community/cli -v` in your terminal and copy the result here.
+      placeholder: "npx @react-native-community/cli -v"
     id: cli
   - type: textarea
     validations:
       required: true
     attributes:
       label: Environment
       description: |
-        Run the command `npx @react-native-community/cli info` in your terminal and copy the results here
-      value: "npx @react-native-community/cli info"
+        Run the command `npx @react-native-community/cli info` in your terminal and copy the result here.
+      placeholder: "npx @react-native-community/cli info"
       render: markdown
     id: env
   - type: textarea
     attributes:
       label: Community Modules
-      description: Describe what you community modules you have added to your project. Not sure? Look at your app's `package.json` and share what's in the "dependencies" section.
+      description: |
+        Describe what you community modules you have added to your project.
+        
+        Not sure? Look at your app's `package.json` and share what's in the "dependencies" section.
     id: modules
+  - type: dropdown
+    validations:
+      required: true
+    attributes:
+      label: Target React Native Architecture
+      description: |
+        Which React Native architecture(s) are you using?
+        
+        Not sure? Which template did you use when creating your project? For RNW <= 0.79.0, the default for new app projects is "Old Architecture".
+        
+        See [New vs. Old Architecture](https://microsoft.github.io/react-native-windows/docs/new-architecture) for more details.
+      multiple: true
+      options:
+        - "New Architecture (WinAppSDK)"
+        - "Old Architecture (UWP)"
   - type: dropdown
     attributes:
       label: Target Platform Version
-      description: What SDK version are you building for?
+      description: What Windows SDK version are you building for?
       options:
-        - "10.0.15063"
-        - "10.0.16299"
+        - "<= 10.0.17763"
+        - "10.0.17763"
+        - "10.0.18362"
         - "10.0.19041"
         - "10.0.22000"
-        - "10.0.22321"
         - "10.0.22621"
+        - "10.0.26100"
+        - ">= 10.0.26100"
     id: sdk
-  - type: dropdown
-    attributes:
-      label: Target Device(s)
-      description: What device(s) are you targeting?
-      multiple: true
-      options:
-        - "Desktop"
-        - "Xbox"
-        - "HoloLens"
-    id: device
   - type: dropdown
     attributes:
       label: Visual Studio Version
       description: Which version of Visual Studio are you using?
       options:
-        - "Visual Studio 2017"
-        - "Visual Studio 2019"
         - "Visual Studio 2022"
+        - "Visual Studio 2022 Preview"
     id: vs
   - type: dropdown
     attributes:
@@ -94,18 +113,13 @@ body:
         - "Release"
         - "ReleaseBundle"
     id: config
-  - type: markdown
-    attributes:
-      value: |
-        **Troubleshooting**
-        If you see build failure on `npx @react-native-community/cli run-windows`, please try again with `npx @react-native-community/cli run-windows --logging` and provide the output.
-    id: troubleshoot
   - type: textarea
     attributes:
       label: Snack, code example, screenshot, or link to a repository
       description: |
         Please provide a [Snack](https://snack.expo.io/), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
+
         You may provide a screenshot of the application if you think it is relevant to your bug report.
+
         [Here are some tips for providing a minimal example](https://stackoverflow.com/help/mcve).
     id: code
-
diff --git a/.github/ISSUE_TEMPLATE/feature-request.yaml b/.github/ISSUE_TEMPLATE/feature-request.yaml
@@ -2,11 +2,16 @@ name: Feature request
 description: Suggest a new feature or idea
 title: Your feature request
 labels: [enhancement]
+type: 'Task'
 body:
   - type: markdown
     attributes:
       value: |
-        This is a template for new feature or API proposals for React Native for Windows. Use this to submit new API/component requests or behavior updates that are specific to Windows. For feature requests to React Native, go [here](https://github.com/react-native-community/discussions-and-proposals) instead. 
+        This form is for new feature or API (modules or components, methods or properties, etc.) proposals for React Native for Windows. Use this to submit new API requests or behavior updates that are *specific* to Windows.
+        
+        If your request is for is an existing React Native API that is simply missing in React Native for Windows, please use the [this form](https://github.com/microsoft/react-native-windows/issues/new?template=missing-api.yaml) instead.
+
+        For feature requests to React Native, go [here](https://github.com/react-native-community/discussions-and-proposals) instead.
         
         Read more about React Native for Windows proposal process [here](https://github.com/microsoft/react-native-windows/tree/main/vnext/proposals).
         
@@ -24,7 +29,10 @@ body:
       label: Motivation
       description: |
         Why are we doing this? What use cases does it support? What is the expected outcome? Why should this be done for Windows?
-        Please focus on explaining the motivation so that if this proposal is not accepted, the motivation could be used to develop alternative solutions. In other words, enumerate the constraints you are trying to solve without coupling them too closely to the solution you have in mind.
+
+        Please focus on explaining the motivation so that if this proposal is not accepted, the motivation could be used to develop alternative solutions.
+        
+        In other words, enumerate the constraints you are trying to solve without coupling them too closely to the solution you have in mind.
   - type: textarea
     attributes:
       label: Basic Example
@@ -34,5 +42,6 @@ body:
     attributes:
       label: Open Questions
       description: |
-        Please list any open issues that you think still need to be addressed.
-        These could include areas you think would benefit from community or the react-native-windows team input
+        Please list any open questions or issues that you think still need to be addressed before this suggestion can be implemented.
+
+        These could include areas you think would benefit from the community or the RNW team's input.
diff --git a/.github/ISSUE_TEMPLATE/integration-follow-up.yaml b/.github/ISSUE_TEMPLATE/integration-follow-up.yaml
@@ -1,42 +1,45 @@
 name: Integration Follow-up Report
 description: File an integration follow-up issue
 labels: [Integration Follow-up]
+type: 'Task'
 body:
   - type: markdown
     attributes:
       value: |
+        This form is for reporting issues in React Native for Windows arising from integrating upstream `react-native` code, where the issues were worked-around or fixed locally to unblock the integration, but will need some follow-up afterward.
+
         Your issue will be triaged by the RNW team according to [this process](https://github.com/microsoft/react-native-windows/wiki/Triage-Process).
   - type: textarea
     validations:
       required: true
     attributes:
       label: Problem Description
-      description: This form is for reporting errors arising from Meta integrations. Please provide a detailed description of the issue and any relevant information that may assist in debugging.
+      description: Please provide a detailed description of the issue and any relevant information that may assist in debugging.
     id: description
-  - type: textarea
+  - type: input
     validations:
       required: true
     attributes:
-      label: Link to the integration where the error originated
+      label: Link to the integration PR where the error originated
     id: integration
   - type: textarea
     validations:
       required: true
     attributes:
-      label: Link to commit
+      label: Link to `react-native` commit
       description: Please link the specific commit from upstream that introduced the issue. If the exact commit is unknown, provide the range of commits brought in from the integration.
     id: commit
   - type: textarea
     attributes:
       label: Forked files
-      description: If any files were forked from upstream, list them below and ensure that any Windows-specific changes in those files are enclosed in [Windows] comments."
+      description: If any files were forked from upstream, list them below and ensure that any Windows-specific changes in those files are enclosed in [Windows] comments.
       placeholder: |
         1.
         2.
     id: files
   - type: textarea
     attributes:
-      label: Upstream PR
+      label: Upstream PR in `react-native`
       description: If an upstream PR has already been made, please link it and add the date the fork can be removed.
     id: upstream
   - type: dropdown
diff --git a/.github/ISSUE_TEMPLATE/missing-api.yaml b/.github/ISSUE_TEMPLATE/missing-api.yaml
@@ -0,0 +1,58 @@
+name: Missing React Native API on Windows
+description: Report that a React Native API is missing on Windows
+title: Implement <missing API name> for <architecture>
+labels: ['enhancement', 'API: Completion']
+type: 'Task'
+body:
+  - type: markdown
+    attributes:
+      value: |
+        This form is to report APIs (methods or properties, etc.) which exist in React Native for iOS/Android but are missing or otherwise not implemented in React Native for Windows.
+
+        If the API does not exist in React Native, please use the [this form](https://github.com/microsoft/react-native-windows/issues/new?template=feature-request.yaml) instead.
+        
+        Your issue will be triaged by the RNW team according to [this process](https://github.com/microsoft/react-native-windows/wiki/Triage-Process).
+  - type: input
+    validations:
+      required: true
+    attributes:
+      label: APInName
+      description: What is the name of the missing API (including module or component name)?
+      placeholder: API Name
+  - type: dropdown
+    validations:
+      required: true
+    attributes:
+      label: API Type
+      description: What is the type of the missing API?
+      options:
+        - "Component Method"
+        - "Component Property"
+        - "Module Method"
+        - "Module Property"
+        - "Other"
+    id: type
+  - type: input
+    validations:
+      required: true
+    attributes:
+      label: React Native Docs URL
+      description: Where is the API documented on reactnative.dev?
+      placeholder: https://reactnative.dev/docs/components-and-apis
+    id: url
+  - type: dropdown
+    validations:
+      required: true
+    attributes:
+      label: Supported Architecture
+      description: For which React Native architecture is the API supported?
+      options:
+        - "Both Architectures"
+        - "New Only"
+        - "Old Only"
+    id: architecture
+  - type: textarea
+    attributes:
+      label: Other Details
+      description: Please add any other details that may be relevant to implementing this API.
+    id: details
