chore: require build number in bug report template

[gauthierpetetin]

Description

The purpose of this PR is to require a build number in the Mobile bug report template.

Changelog

CHANGELOG entry: null

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

---

Note

Adds a required Build number field to the bug report template and clarifies the Version field description.

• GitHub Issue Template:
  • Bug report (.github/ISSUE_TEMPLATE/bug-report.yml):
    • Add required Build number input field.
    • Update Version field description to reference "About MetaMask".

^{Written by Cursor Bugbot for commit d4d4020. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 100%

click to see 🤖 AI reasoning details

The change is to a GitHub issue template file (.github/ISSUE_TEMPLATE/bug-report.yml) which is purely for documentation and process purposes. The changes are:

1. Updated the description text for the "Version" field to be more specific: "Settings > About" → "Settings > About MetaMask"
2. Added a new "Build number" field to the bug report template, requesting users to provide the build number (found in "Settings > About MetaMask")

These changes affect only the bug reporting process and have no impact on:

• Application code
• Runtime behavior
• User-facing functionality
• E2E test infrastructure
• Build processes
• CI/CD pipelines (beyond the template itself)

This is purely a documentation/process improvement that helps gather more detailed information from users when they submit bug reports. No code functionality is modified, and therefore no E2E tests need to be run to verify these changes.

View GitHub Actions results

[cursor]

Bug: Build number field id uses space instead of hyphen

The id field for the new build number input uses build number with a space, breaking the established convention in this template. Other multi-word field IDs use hyphens (e.g., what-happened, expected-behavior, screenshot-recording). The field id should be build-number to maintain consistency and avoid potential issues with GitHub's form processing, which typically treats identifiers with spaces as problematic.

 

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud