Skip to content

Bug 2036191 - Crash Signature Field Mismatch in Bugzilla REST API#2612

Open
dklawren wants to merge 2 commits into
mozilla-bteam:masterfrom
dklawren:2036191
Open

Bug 2036191 - Crash Signature Field Mismatch in Bugzilla REST API#2612
dklawren wants to merge 2 commits into
mozilla-bteam:masterfrom
dklawren:2036191

Conversation

@dklawren
Copy link
Copy Markdown
Collaborator

@dklawren dklawren commented May 1, 2026

No description provided.

Copilot AI review requested due to automatic review settings May 1, 2026 16:38
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR addresses a Bugzilla REST API inconsistency where cf_crash_signature (and other custom fields) may be stored on a bug but omitted from REST responses due to product/component visibility filtering.

Changes:

  • Add “Web Compatibility” to the product allowlist for cf_crash_signature visibility.
  • Update REST bug serialization to also emit non-empty values for custom fields that are not enabled for the bug’s product/component.
  • Update bug update logic (set_all) to only set custom fields that are enabled for the bug’s current product/component.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File Description
extensions/BMO/lib/Data.pm Expands cf_crash_signature visibility to include the “Web Compatibility” product.
Bugzilla/WebService/Bug.pm REST: emits stored values for non-enabled custom fields when non-empty.
Bugzilla/Bug.pm Limits which custom fields set_all will set based on product/component-enabled custom fields.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread Bugzilla/WebService/Bug.pm Outdated
Comment thread Bugzilla/WebService/Bug.pm Outdated
Comment thread Bugzilla/WebService/Bug.pm Outdated
@dklawren dklawren requested a review from cgsheeh May 1, 2026 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants