OrgTriage — Salesforce Org Health

Turn Salesforce org findings into a prioritized backlog. Read-only org-health checks across ten areas, exported as Jira work items.

Turn Salesforce org findings into a prioritized backlog. Assess org health, rank issues by impact, and create actionable Jira work items. Org-health checks for Salesforce admins, in Chrome's side panel beside Lightning, so it stays open while you work through the org. No managed package, nothing to install in the org, nothing to configure. Every finding becomes a backlog item with steps, acceptance criteria and an estimate; the Jira export creates Bugs and Tasks. TEN ANALYZERS Apex — org-wide and per-class coverage against the 75% deployment gate, components with no coverage, triggers at 0%, multiple active triggers on one object, stale API versions, components needing recompile, missing exception-email recipients, and stale or failing test runs. Flows — DML and SOQL inside a loop, found by walking the flow graph rather than by matching names; data elements with no fault path; record-triggered flows with no entry criteria; trigger-order collisions; Process Builder and workflow-era automation still in place; never-activated flows; version clutter; and legacy Cloud Flow Designer flows. Reports & Dashboards — unfiltered full-object scans identified from metadata without ever executing a report, filters on unindexed custom fields, abandoned reports, hidden report types, private and unfiled folders, structurally duplicated reports, dashboard components pointing at deleted reports, and dashboards that multiply report runs through filters. Layouts & SLDS — field-heavy layouts, oversized sections, layouts near the 100 related-list limit, Lightning page regions past the documented components-per-region limit, and a full SLDS 2 conformance pass over your custom Aura and LWC stylesheets. Ops — the run-time problems that only surface on scattered Setup pages: batch, queueable and future jobs failing this week; scheduled jobs in an error or blocked state; scheduled jobs owned by a deactivated user, which is how a nightly process silently stops; hours of the day with jobs stacked up; failed and long-paused flow interviews; approvals pending for a month or assigned to a deactivated approver; and who is calling your API. Access — who holds Modify All Data, View All Data, Author Apex, Customize Application and Manage Users, by which route (profile, permission set, or group), whether they still log in, permission sets nobody is assigned to, and assignments still held by deactivated users. Security settings — Salesforce's own Health Check risks, read from the SecurityHealthCheck objects, turned into stories with owners and estimates and compared against the previous scan. Limits and storage — data and file storage headroom, debug-log storage, the governor limits nearest their ceiling, and where the storage went. Fields — custom fields referenced by no Apex class, flow or validation rule (layouts, pages and reports are not read, and every finding says so), fields with no description, and validation rules that hard-code a record id. Apex code quality — the source actually deployed in the org: queries and DML inside loops, classes with no sharing declaration, empty catch blocks, hard-coded ids, and unbounded queries. Text checks, biased to under-report, and labelled as such. HONEST BY DESIGN - Nothing refreshes automatically. A scan happens because you pressed a button. - Every scan reports exactly how many API calls it spent. - Reports are never executed, without exception — your org's synchronous report runs are untouched. Per-user API usage is linked to its two Salesforce sources, not computed. - A rule that could not be evaluated is reported as "not evaluated", never as a pass. - Truncated scans say how many components were not inspected. - Thresholds Salesforce does not publish are labelled as OrgTriage recommendations, and each rule that rests on documentation links to it. - Export any remediation plan to CSV or Markdown, or print it. PRIVACY - No account, no sign-up, no password. OrgTriage reuses the Salesforce session your browser already holds. - No servers, no analytics, no telemetry. Nothing is transmitted anywhere except to your own Salesforce org — the extension's Content Security Policy makes any other destination impossible. - Your session token is used only inside the service worker to authenticate requests to your own Salesforce org. It is never passed to the panel, never written to disk, and never sent anywhere else. - Three permissions: cookies, storage and sidePanel. No access to any non-Salesforce site. - Reads configuration metadata and Apex source — never your business records. The people-related fields it reads for the Ops, Access, Limits and Reports analyzers are listed, exactly, in the privacy policy. OrgTriage is a diagnostic tool, not an adviser, and is provided as is. Every finding is a recommendation: have an experienced Salesforce administrator or developer verify it and test the change outside production. Not affiliated with, endorsed by, or sponsored by Salesforce, Inc. From Everything Virtually LLC, Austin, Texas.