Skip to content

Conversation

@Mihir-Mavalankar
Copy link
Contributor

@Mihir-Mavalankar Mihir-Mavalankar commented Nov 12, 2025

PR Details

  • Removing the Scan issues setting for projects under the triage signals feature flag.
  • Post launch, new orgs will have it set to True since the default is True and existing orgs that explicitly set it to False will still have it as False
  • Implementation notion doc link

@Mihir-Mavalankar Mihir-Mavalankar self-assigned this Nov 12, 2025
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Nov 12, 2025
),
fields: [
seerScannerAutomationField,
...(isTriageSignalsFeatureOn ? [] : [seerScannerAutomationField]),
Copy link
Contributor

Choose a reason for hiding this comment

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

Bug: Phantom Toggle Hides Automation Fields

When the triage-signals-v0 feature is enabled and seerScannerAutomation is false, the autofixAutomatingTuningField and automatedRunStoppingPointField will be hidden because their visible conditions check model?.getValue('seerScannerAutomation') === true. Removing the seerScannerAutomationField from the form doesn't change the underlying value, causing the dependent automation fields to remain hidden even though the toggle is no longer accessible to users.

Fix in Cursor Fix in Web

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes that is true. It's an edge case we discussed on #proj-triage-signals and we are okay with it.

@kddubey
Copy link
Contributor

kddubey commented Nov 12, 2025

i (🐒) do not know frontend. deferring to @roaga on this one

@Mihir-Mavalankar Mihir-Mavalankar merged commit 5136da9 into master Nov 12, 2025
51 checks passed
@Mihir-Mavalankar Mihir-Mavalankar deleted the removescan-issues-ui branch November 12, 2025 17:05
andrewshie-sentry pushed a commit that referenced this pull request Nov 13, 2025
…103205)

## PR Details
+ Removing the Scan issues setting for projects under the triage signals
feature flag.
+ Post launch, new orgs will have it set to True since the default is
True and existing orgs that explicitly set it to False will still have
it as False
+ Implementation notion doc
[link](https://www.notion.so/sentry/Triage-Signals-V0-Technical-Implementation-Details-2a18b10e4b5d8086a7ceddaf4194849a?source=copy_link#2a18b10e4b5d80869424fb52219c3ce9)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants