Skip to content

Conversation

@ryan953
Copy link
Member

@ryan953 ryan953 commented Jan 31, 2026

Page Img
Main Settings SCR-20260131-jtvd
Project List SCR-20260131-jrqc
Project Details SCR-20260131-jrow

Fixes CW-733

@ryan953 ryan953 requested a review from a team as a code owner January 31, 2026 18:42
@linear
Copy link

linear bot commented Jan 31, 2026

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jan 31, 2026
Copy link
Contributor

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 3 potential issues.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

)}
</Flex>
),
key: 'pr_creation',
Copy link
Contributor

Choose a reason for hiding this comment

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

Bulk action bypasses enableSeerCoding restriction for PR Creation

Medium Severity

The PR Creation column header tooltip and individual row switches correctly check organization.enableSeerCoding === false to disable the feature, but the bulk action DropdownMenu for "PR Creation" (shown when projects are selected) only checks canWrite. Users can bypass the enableSeerCoding restriction by selecting multiple projects and using the bulk dropdown to enable PR creation, even when code generation is disabled at the org level.

Additional Locations (1)

Fix in Cursor Fix in Web

)}
</Alert>
)}
</Flex>
Copy link
Contributor

Choose a reason for hiding this comment

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

Settings toggle not disabled when code generation disabled

Medium Severity

The autoOpenPrs field shows an Alert warning when organization.enableSeerCoding === false, but unlike the project-level components (seerAgentSection.tsx and seerProjectTableRow.tsx), it doesn't disable the toggle. This allows users to enable the setting despite the warning that it won't work. The field definition supports a disabled property (as seen in the form types), but one isn't provided for this case, creating inconsistent behavior across the UI.

Fix in Cursor Fix in Web

),
}
)}
</Alert>
Copy link
Contributor

Choose a reason for hiding this comment

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

Duplicated warning message pattern across three files

Low Severity

The identical tct('[settings:"Enable Code Generation"] must be enabled...') message with the same Link to={...seer/#enableSeerCoding} pattern is duplicated across three files. Consider extracting this into a shared helper function or constant (e.g., getSeerCodingDisabledMessage(orgSlug)) to reduce maintenance burden.

Fix in Cursor Fix in Web

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.

2 participants