Home CodePerformance

CodePerformance

AI-powered performance review for faster, more efficient code.
By Vishwesh
24 articles

How do I select multiple issues and perform bulk actions like changing status or assigning?

Short Answer: Select issues using the checkboxes; when one or more are selected, the bulk action bar appears with "Change status" and "Assign to" controls. PreRequisites 1. Be signed in (required to modify issues in most org setups). 2. Open the repository Issues page. Steps 1. Select multiple issues by checking their row checkboxes, or use the header checkbox to select all visible rows. A top bulk action bar appears showing “8 selected” (or the number selected). 2. To change the status for the selected issues, click the "Change status" dropdown in the bulk action bar. Status options are shown (e.g., Resolved, In progress). 3. Choose the new status. Confirm if prompted. The selected issues update to the new status, and the status badges refresh. 4. To assign selected issues, click "Assign to" in the bulk action bar and choose a user. The Assignee column updates for the selected issues. 5. When finished, click "Clear selection" (or the X) on the bulk bar to exit bulk mode. The bulk action bar closes and the normal issue list view returns. Troubleshooting 1. Bulk actions are not available after selecting issues. Likely Cause: No issues are actually selected, or you lack permission to update issues. Action: Verify the checkboxes are checked (the selected count should appear in the bulk action bar). If still unavailable, sign in or contact your admin for appropriate permissions. 2. Bulk status or assignment changes don’t apply to some items. Likely Cause: Some issues may be in a state or scope that prevents changes (e.g., already closed or restricted by policy). Action: Try updating a single issue first to identify if a specific item blocks the action, then adjust accordingly. Note: Bulk actions apply only to the currently visible and selected rows — not to all pages — unless you explicitly select them.

Last updated on Feb 23, 2026

How do I share a performance review and control access (Private vs Public)?

Short Answer: Click "Share", enter email(s) in "Enter email address", choose a role (Member), set Document access to "Private" or "Public", then click "Copy link" or "Save". PreRequisites 1. Be signed in (recommended for sending invites). 2. Open the repository Issues page and click the top-right "Share" button. Steps 1. Click the "Share" button in the top-right of the Issues page. The "Share performance review" modal opens. 2. In the modal, add teammates’ email addresses in "Enter email address" and use the role dropdown (default shows "Member") to set their access role. Entered emails appear in the invite field and will be granted the selected role. 3. Review the "People with access" list to confirm who already has access and their assigned role (e.g., Richard Roe — Admin, Jane Doe — Member). Existing users and their access roles are visible. 4. Under "Document access", choose "Private" (only team members can view) or "Public" (anyone with the link can view). The selection is applied, and the description updates (for Public, it shows: "Anyone with the link can view. No login required."). 5. If you need a shareable link immediately, click "Copy link". To apply changes, click "Save". To exit without saving, click "Cancel" or the X. "Copy link" copies the URL, while "Save" persists the access settings and closes the modal. Troubleshooting 1. The Share button does not open the modal. Likely Cause: You are not signed in, or the page did not load correctly. Action: Click "Sign In" (top-right if visible) and try again. Refresh the page if needed. 2. You accidentally set Document access to "Public" and want to revoke it. Likely Cause: Public access allows anyone with the link to view the document. Action: Reopen "Share", switch Document access back to "Private", and click "Save" to restrict access. Note: Setting Document access to Public allows viewing by anyone with the link (no login required). Use this setting cautiously for sensitive repositories or performance reviews.

Last updated on Feb 23, 2026

How do I view the issues list for a repository?

Short Answer: Open the repository Issues page (URL: /services/codeperformance/review/orgid/repo/branch/issues) to see the top summary and the issues list with status and assignee columns. PreRequisites 1. Open the repository Issues page (URL shown above). 2. Be signed in if your organization requires authentication. Steps 1. Open the repository Issues page (example path: /services/codeperformance/review/orgid/repo/branch/issues). You see the page header and breadcrumb (e.g., CodePerformance › FastAPI (main) › Issues). 2. Review the top summary card showing "Total issues", "By status", and "By severity". Counts and status/severity badges are visible (for example: Open, In progress, Resolved, Closed, Rejected; High, Medium, Low). 3. Scroll down to the issues list. Review each row for the issue title, file path tag, status badge, and assignee column. You may see entries like "SQL Injection in raw SQL query" with file tag (e.g., src/api/user.js), Status (Open), and Assignee (Alice). 4. Use the pagination controls at the bottom (e.g., "Showing 1–25 of 232") to move between pages. The page updates to display the selected set of issues. Troubleshooting 1. The page shows "No issues found yet". Likely Cause: No issues exist in the repository, or active filters are hiding all results. Action: Clear filters (set "All severity", "All status", "All assignees", "All files") and run the search again. See screen_0.png. 2. The top banner reads "Reviewing 7 of 25 files…" and some issues are missing. Likely Cause: The repository scan/review is still running, so results are partial. Action: Wait for the review process to finish (the banner will disappear), or refresh the page after a minute. Note: The breadcrumb and "Last reviewed" timestamp help confirm which repository/branch you are viewing and how recent the issue data is.

Last updated on Feb 23, 2026

What do the top summary items mean (Total issues, By status, By severity)?

Short Answer: "Total issues" shows the overall count. "By status" shows counts per status (Open, In progress, Resolved, Closed, Rejected). "By severity" shows counts by severity (High, Medium, Low). PreRequisites 1. Open the repository Issues page. Steps 1. Look at the summary card under the breadcrumb. Read "Total issues" for the overall count. You will see the numeric total (for example, 20). 2. Check the "By status" badges next to "Total issues" to see how many issues are Open, In progress, Resolved, Closed, or Rejected. Each status badge shows a count (example: Open: 4, In progress: 3, Resolved: 1, Closed: 0, Rejected: 12). 3. Review the "By severity" badges to see counts of High, Medium, and Low severity issues. The severity badges display totals (example: High: 3, Medium: 3, Low: 2). 4. Use these counts to guide filtering. Click related filters or combine them with search to narrow results. You can quickly refine the issues list using the visible summary numbers and filter controls. Troubleshooting 1. The counts don’t match what you see in the issue list. Likely Cause: Active filters or a partial repository scan/review may cause discrepancies. Action: Clear active filters, wait for any review process to finish, and refresh the page to get updated counts. Note: The summary counts reflect the currently indexed data. They automatically update when new scans complete or when filters change the visible scope.

Last updated on Feb 23, 2026

Why does the page say "No issues found yet" or show fewer issues than expected?

Short Answer: Common causes include active filters hiding results, a repository scan still running ("Reviewing ... files"), or there truly being no issues in the selected scope. PreRequisites 1. Open the repository Issues page. Steps 1. Check the top summary and the filter row. Set "All severity", "All status", "All assignees", and clear "All files" selections. Once filters are reset, any hidden issues will reappear if present. 2. Look for a banner that says "Reviewing X of Y files…". If visible, wait until the review process completes. When the repository scan finishes, the issue list updates with additional results. 3. Use the search box to look for a known issue title or filename, and check pagination controls at the bottom for other pages. If the issue exists, it should appear in search results or on another page. 4. If the page still shows zero or fewer issues than expected, refresh the page or sign in and try again. A page reload may surface updated results. Troubleshooting 1. Filters appear cleared, but no issues are visible. Likely Cause: The review job is still running, or results are temporarily delayed. Action: Wait for the "Reviewing ... files" banner to disappear, then refresh the page. 2. You cannot see expected issues, while others can. Likely Cause: Permissions or sign-in status differ between users. Action: Click "Sign In" (top-right) or contact your repository admin to verify access permissions. Note: Check the "Last reviewed" timestamp in the page header to confirm how recent the repository scan is.

Last updated on Feb 23, 2026

How do I re-run the AI code review for this pull request

Short Answer: Click 'Re-run review', confirm in the 'Confirm re-run review' modal, then wait while the progress banner shows 'Reviewing X of Y files...'. PreRequisites 1. Be signed in. 2. Open the relevant pull request (PR) page. Steps 1. Click the 'Re-run review' button in the PR header. The 'Confirm re-run review' modal appears. 2. Read the warning message: "Re-running this review will replace previous AI-generated findings with updated results based on the latest code." Then click 'Re-run review' to proceed (or 'Cancel' to stop). The modal closes and the AI code review re-run begins. 3. Watch the progress banner that appears (for example: 'Reviewing 7 of 25 files...'). A loading state is displayed while files are being analyzed. 4. Once the re-run completes, review the updated 'Total issues' count and refreshed issue list. The issue counts and rows now reflect the new AI analysis. Troubleshooting 1. The review remains on 'Reviewing X of Y files...' for an extended time. LikelyCause: A large codebase or temporary backend delay. Action: Wait a few minutes and refresh the page if progress does not update. If the issue persists, try re-running the review later or contact support. 2. You re-ran the review but want the previous results back. LikelyCause: A re-run replaces previous AI-generated findings, and there is no in-app undo option. Action: Before re-running, use 'Share', 'Copy link', or export options (if available) to preserve results. If already replaced, check with teammates for saved copies. Note: Re-running the AI code review replaces the current findings with newly generated results based on the latest code at the time of execution.

Last updated on Feb 23, 2026

How do I view the list of issues for this pull request (eg: PR #123)?

Short Answer: Open the pull request (PR) page (e.g., PR #123). The top summary shows 'Total issues' with colored badges for 'By status' and 'By severity'; the issue table below lists each finding with severity, file path, status, and assignee. PreRequisites 1. Be signed in to Everdone. 2. Open the pull request page (e.g., PR #123). Steps 1. Open the pull request page for PR #123 (example PR header: 'PR #123 — Add payment gateway integration'). You see the PR header and the summary card. 2. Review the summary card labeled 'Total issues' and the 'By status' and 'By severity' badges. The counts and colored badges are visible (for example, 'Open: 4', 'High: 3'). 3. Scroll to the issue table below the filters to view each issue row. Each row shows a severity label, issue title, file path tag (e.g., 'src/api/user.js · main · lines 52–63'), a status badge, and an Assignee column. Troubleshooting 1. The page shows 'No issues found'. Likely Cause: The review returned zero findings for this PR. Action: If you expect findings, click 'Re-run review' to scan the latest code, or verify the PR contains relevant code changes. 2. The page shows 'No matching issues' even though 'Total issues' > 0. Likely Cause: Active filters or a search query is hiding results. Action: Clear or adjust filters (All severity, All status, All assignees, All files) and clear the search box. Note: Issue rows include the file path and line numbers so you can jump directly to the exact code location.

Last updated on Feb 23, 2026

Why is the issue page empty or why can't I see issue details?

Short Answer: If the issue details area is empty or doesn’t load, you’re likely not signed in or the page failed to load fully; sign in and refresh the page. PreRequisites 1. (Optional) Have access to the repository/review where the issue exists. Steps 1. Check the top-right of the page for 'Sign In' or your avatar — if it shows 'Sign In', you are not logged in. This confirms whether you are signed in. 2. Click 'Sign In', sign into your account, then reopen the issue. The issue content should load for authenticated users. 3. If you are signed in but the content is still blank, reload the page (hard refresh) and disable extensions that might block site scripts. After reload, the page should render normally and issue details should appear. 4. If the problem persists, test in a different browser or network and report the issue to your admin/support team with screenshots. This helps support investigate server-side or account issues. Troubleshooting 1. The breadcrumb and header show, but the main content area is blank. Likely Cause: Partial page load, or scripts are blocked by a browser extension. Action: Disable blocking extensions, allow site scripts, refresh the page, and sign in if prompted. 2. The Share modal appears but the rest of the page is empty. LikelyCause: A modal overlay is active and hiding the page content. Action: Close the modal using X or 'Cancel'. If the modal is stuck, refresh the page after signing in. Note: When you’re not logged in, the header typically shows 'Sign In' and 'Start For Free'

Last updated on Feb 23, 2026

The issue page looks blank — why can’t I see the issue content?

Short Answer: A blank issue page can indicate you’re not signed in, lack permissions, or there’s a loading error — try signing in and reloading the page. PreRequisites 1. A working browser with JavaScript enabled. 2. A stable internet connection. Steps 1. Check the top-right of the page for a 'Sign In' or 'Start For Free' button (if present, you may be logged out). If 'Sign In' is visible, you are not signed in. 2. If signed out, click 'Sign In' and authenticate using your account. After login, you should be redirected back to the issue page. 3. Reload the issue page after signing in. The issue content (title, code snippet, right panel, and other details) should now be visible. 4. If the page still appears blank, try a different browser or disable browser extensions, then reload. If the issue is environment-specific, the page should render correctly in the alternative setup. Troubleshooting 1. The page shows only the header and breadcrumbs, but the main content area is blank. Likely Cause: Session expired, not signed in, or a client-side loading error. Action: Sign in (top-right), refresh the page, or try a different browser. If the issue persists, contact support. 2. Content intermittently fails to load. Likely Cause: Network instability or a temporary backend outage. Action: Check your internet connection, wait a few minutes, and reload the page. Note: If you see breadcrumbs and a 'Share' button but no main content, it usually indicates the page failed to fully render the issue details.

Last updated on Feb 23, 2026

How do I filter issues by severity, status, assignee or file?

Short Answer: Use the filter row: click "All severity", "All status", "All assignees", or "All files" and pick the option(s). Use the file picker under "All files" to choose specific files. PreRequisites 1. Open the repository Issues page (e.g., /services/codeperformance/review/orgid/repo/branch/issues). 2. Be signed in if your organization requires authentication. Steps 1. Locate the filter row under the top summary. It includes dropdowns for "All severity", "All status", "All assignees", "All files", plus the search field. All four dropdown controls and the search input are visible. 2. To filter by severity, click "All severity" and choose a level (e.g., High, Medium, Low). The issue list updates to show only issues matching the selected severity. 3. To filter by status, click "All status" and choose a status (e.g., Open, In progress, Resolved, Rejected). The list updates to match the selected status filter. 4. To filter by assignee, click "All assignees" and select a person. Only issues assigned to that assignee are shown. 5. To filter by file(s), click "All files" to open the file picker. Search for files or expand folders, then check the file(s) you want. The list shows only issues located in the selected file(s). Troubleshooting 1. No issues appear after applying filters. LikelyCause: Filters are too restrictive or conflicting (for example, severity + status + file with no overlapping results). Action: Reset filters to "All severity", "All status", "All assignees", and clear the file selection. Then apply filters one at a time to identify the conflicting filter. 2. The file picker shows no matching files when searching. Likely Cause: The path/query is incorrect, or the repository file tree is still being indexed. Action: Try a broader file search, or wait for the "Reviewing ... files" banner to finish, then open the file picker again. Note: You can combine filters (severity + status + assignee + files) to narrow results. The top "By status" and "By severity" badges reflect the current scope and may update when filters are applied.

Last updated on Feb 23, 2026

How do I filter issues to specific file(s) using the "All files" picker?

Short Answer: Click "All files", use the file picker tree or "Search files..." to find and check file(s); the issue list will then show only issues from those selected files. PreRequisites 1. Open the repository Issues page. 2. The repository file tree must be indexed (the file picker populates after the review/scan completes). Steps 1. Click the "All files" dropdown in the filter row. The file picker opens showing "Search files..." and a folder/file tree (e.g., src, tests). 2. Use the "Search files..." input to find a file, or expand folders to locate the file you want. Matching files are highlighted or visible under their folders. 3. Check the box next to one or more files (for example, select "user.js" under src). Selected files show checkmarks. The picker stays open until you click outside or close the dropdown. 4. Click outside the picker (or use the picker’s close affordance) to apply the selection. The issue list updates to show only issues from the selected file(s). Troubleshooting 1. No files appear in the file picker. Likely Cause: The repository scan/review is still running, or the app can’t access the repository file tree. Action: Wait for the "Reviewing ... files" banner to finish, then reopen the picker. If it still doesn’t populate, refresh the page. 2. Selecting a file doesn’t change the issue list. Likely Cause: Another active filter (status, severity, assignee, or search) is hiding results. Action: Clear other filters and the search box, then retry the file selection. Note: The file picker supports folder expansion and file search. Selected files combine with other active filters (they apply together to narrow results).

Last updated on Feb 23, 2026

How do I copy the suggested fix so I can apply it locally?

Short Answer: Click the "Copy" button in the "Suggested fix" panel, then paste the copied code into your local editor to apply, test, and commit outside the app. PreRequisites 1. Be signed in if required. 2. Allow clipboard access in your browser (accept clipboard prompts if shown). Steps 1. Scroll to the "Suggested fix" panel on the issue page. You’ll see the suggested fix code and a "Copy" button in the panel. 2. Click the panel’s "Copy" button (top-right of the Suggested fix box). The suggested fix code is copied to your clipboard. 3. Paste the copied code into your local editor, then test and commit changes in your repository as appropriate. The suggested fix appears in your editor for editing and testing. 4. If you need more context, use "View full file" and copy surrounding lines manually. You can capture additional lines around the snippet for correct placement. Troubleshooting 1. Clicking "Copy" does not put code on the clipboard. Likely Cause: Browser clipboard permission is blocked, or the button action failed. Action: Manually select the code text and press Ctrl/Cmd + C. If manual copy works but the button doesn’t, enable clipboard permissions for the site in your browser settings and try again. Note: The Suggested fix panel provides an example snippet (for instance: if (!user) return null; return user.name.toUpperCase();). Always review and adapt it to match your codebase before committing.

Last updated on Feb 23, 2026