Home CodeSecurity

CodeSecurity

AI-powered security review for safer production code.
By Vishwesh
• 25 articles

How do I select multiple issues and apply a bulk action (change status or assign)?

Short Answer: Select issue checkboxes (or the header checkbox), then use the top action bar that appears (Change status or Assign to) to apply bulk changes. PreRequisites 1. Repository Issues page is open 2. Page has finished loading Steps 1. Select issues by clicking the checkboxes on the left of each issue row (or use the header checkbox to select all visible rows). Selected rows show a checkmark and a blue top bar appears showing “8 selected” (example). 2. In the blue top action bar, click Change status to choose a new status for all selected items. Pick the desired status; it applies to all selected issues. 3. Or click Assign to to assign the selected issues to a user. Selected issues are assigned to the chosen assignee after confirmation. 4. To stop editing, click Clear selection on the action bar. All checkboxes are cleared and the action bar closes. Troubleshooting 1. Change status or Assign to appears but nothing happens after selecting an option. LikelyCause: The page is mid-load or the selection didn’t register. Action: Ensure the page finished loading, re-select the issues, then retry the bulk action. 2. No action bar appears after selecting checkboxes. Likely Cause: A UI glitch or selections were not registered. Action: Deselect then reselect rows or refresh the page and try again. Note: Bulk actions apply only to the currently selected issues (the action bar shows how many are selected).

Last updated on Feb 19, 2026

How do I share the security review and control who can view it?

Short Answer: Click ‘Share’, add emails in ‘Enter email address’ and choose a role, set ‘Document access’ to ‘Private’ or ‘Public’, then click ‘Save’ or use ‘Copy link’. PreRequisites 1. Repository Issues page is open 2. You are signed in Steps 1. Click ‘Share’ in the top-right of the page. The ‘Share security review’ modal opens. 2. Under ‘Share with your team’, type an email into ‘Enter email address’ and choose a role from the dropdown (default: ‘Member’). The email appears in the pending list. 3. Review ‘People with access’ to confirm who already has access and their roles. (e.g., Richard Roe — Admin, Jane Doe — Member, Alex Smith (you) — Owner). 4. Under ‘Document access’, select ‘Private’ or ‘Public’. - Private — “Only team members can view this security review.” - Public — “Anyone with the link can view. No login required.” 5. Click ‘Copy link’ to copy a shareable URL, or click ‘Save’ to apply changes (use ‘Cancel’ to close without saving). Troubleshooting 1. ‘Share’ modal won’t open or ‘Share’ button not visible LikelyCause: Not signed in. Action: Click ‘Sign In’ or ‘Start For Free’ in the header, then try ‘Share’ again. 2. Recipients can’t view the link you shared LikelyCause: ‘Document access’ is set to ‘Private’. Action: Reopen ‘Share’, set ‘Document access’ to ‘Public’ or add the specific emails under ‘People with access’, click ‘Save’, then ‘Copy link’ again. Note: Use ‘Public’ only when you’re comfortable with anyone who has the link being able to view the security review.

Last updated on Feb 19, 2026

How do I view the issue details for?

Short Answer: Open the issue page to see the title, file path, Description, Code snippet, Suggested fix, History, and the right-hand panel (Status, Assignee, Severity). PreRequisites 1. Open the issue URL (repo review). 2. If the review is Private, sign in as a team member or ensure you’ve been granted access. Steps 1. Open the issue URL or navigate from the repository review. Confirm the breadcrumb and title (eg: “Possible null reference when accessing user.name”) are visible. The breadcrumb and issue title appear at the top. 2. Read the Description card for context. Example: db.getUser() may return null. 3. Inspect the Code snippet to see the problematic lines (e.g., lines 52–53). Example snippet: const user = await db.getUser(id); return user.name.toUpperCase(); 4. Review the Suggested fix card; use the Copy button to copy the example fix. You can paste the fix into your editor. 5. Scroll to History to see status/assignee changes and timestamps. History logs prior updates. 6. Use the right-hand panel to view Status, Assignee, Severity, and other metadata. Current values are shown and may be editable based on permissions. Troubleshooting 1. Header and breadcrumbs visible, but content is blank. Likely Cause: You’re not signed in and the review is Private. Action: Click Sign In and authenticate, or ask the owner to make the review Public / add you via Share. 2. ‘View full file’ or ‘Copy’ buttons not visible. Likely Cause: Limited read-only view or insufficient permissions. Action: Sign in and confirm access; ask the review owner to share the review if needed. Note: The file path appears below the title (e.g., src/api/userController.js · Lines 52–63).

Last updated on Feb 19, 2026

How do I change status or assign multiple issues at once?

Short Answer: Select multiple issues using the checkboxes; the selection bar appears with Change status and Assign to controls to update items in bulk. PreRequisites 1. Be signed in 2. You have permission to change issue status or assignees Steps 1. Check the boxes beside each issue row you want to update (or use the header checkbox to select all visible rows). A selection bar appears showing something like “8 selected”. 2. In the selection bar, click Change status and choose the new status (e.g., Resolved, Closed, Open, In progress, Rejected). The selected issues’ statuses are updated. 3. To assign, click Assign to in the same selection bar and pick the assignee from the list. The Assignee column updates for the selected issues. 4. To cancel without changes, click Clear selection in the selection bar. All checkboxes are cleared and the bar closes. Troubleshooting 1. Bulk controls aren’t visible after selecting issues. Likely Cause: No rows actually selected or the UI didn’t register the selection. Action: Uncheck and re-check rows, use the header checkbox to select visible rows, or refresh and try again. 2. Status/assignee change failed for some items. Likely Cause: You lack permission for certain issues or they’re locked by another workflow. Action: Confirm your edit permissions for the repository or check with the review owner. Note: Bulk actions apply only to the currently selected rows (and only the current page unless you explicitly select items on other pages).

Last updated on Feb 19, 2026

How do I view the issue list for a pull request?

Short Answer: Open the pull request page — the issue list appears under the PR header with a summary card (Total issues, By status, By severity) and filter/search controls. PreRequisites 1. Be signed in 2. You have access to the repository or the security review Steps 1. Open the pull request page (look for the breadcrumb: CodeSecurity › Pull requests › PR #123). You’re on the PR page for the review. 2. Confirm the PR header shows the title (e.g., PR #123 — Add payment gateway integration) and repo info (Repo: org/repo-name · Author: john_doe). 3. Find the summary card showing Total issues plus By status and By severity counts. 4. Scroll to the issue list rows. Each row shows a severity badge (High/Medium/Low), issue title, and file path with branch and line numbers (e.g., src/api/user.js · main · lines 52–63). 5. Use the filter row (All severity, All status, All assignees, All files), the search box (Search issue titles, descriptions, or file names...), and the sort dropdown (e.g., Recent) to refine. Troubleshooting 1. Page shows “No issues found” or list is empty. Likely Cause: No detected issues for this PR or filters/search are hiding results. Action: Reset to All severity, All status, All assignees, All files and clear the search box. If you still expect issues, click Re-run review to refresh results. Note: The By status and By severity counters sit above the filters to give a quick snapshot before you drill into rows.

Last updated on Feb 19, 2026