Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report_android.yml
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,22 @@ body:
validations:
required: true

- type: dropdown
id: other_error_monitoring_solution
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent field ID naming across templates

Low Severity

The Android template uses id: other_error_monitoring_solution while the Java template uses id: other_error_monitoring. The PR reviewer explicitly requested renaming to other_error_monitoring for consistency, which was applied to the Java template but not the Android template. This inconsistency makes it harder to correlate the same field across templates when processing or querying issue data.

Additional Locations (1)
Fix in Cursor Fix in Web

attributes:
description: Are you using any other error monitoring solution alongside Sentry?
label: Other Error Monitoring Solution
options:
- "No"
- "Bugsnag"
- "Datadog"
- "Firebase Crashlytics"
- "Instabug/Luciq"
- "NewRelic"
- "Other (please mention in issue description)"
validations:
required: true
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Android template lacks separate name input field

Medium Severity

The Android template uses a dropdown with specific solution names and an "Other" catch-all, while the Java template uses a Yes/No dropdown paired with a separate other_error_monitoring_name input field. This design inconsistency means users on the Android template who select "Other" have no structured field to specify which solution they use — they're told to mention it in the issue description, which is easy to forget and harder to parse for triage automation.

Fix in Cursor Fix in Web


- type: input
id: version
attributes:
Expand Down
19 changes: 19 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report_java.yml
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,25 @@ body:
validations:
required: true

- type: dropdown
id: other_error_monitoring
attributes:
description: Are you using any other error monitoring solution alongside Sentry?
label: Other Error Monitoring Solution
options:
- "Yes"
- "No"
validations:
required: true

- type: input
id: other_error_monitoring_name
attributes:
label: Other Error Monitoring Solution Name
description: If you're using another error monitoring solution side-by-side, please enter the name of the other solution.
validations:
required: false

- type: input
id: version
attributes:
Expand Down
Loading