Linking and escalation

Find related work

Open a case and choose the Linked tab, then Search Jira and Slack. Arcus ranks and de-duplicates related Jira issues and Slack threads. Reading never writes anywhere.

Every write needs your approval

• Filing a Jira bug or feature request, linking an existing issue, or pinging an engineer on Slack opens an approval card showing the exact text that will be written
• Each approval is single-use, tied to you, and expires after 30 minutes. If the content changes, it must be approved again
• Possible duplicates are shown first, with a suggestion to link instead
• Missing fields are listed; the button changes to Approve anyway
• Esc skips, ⌘↵ approves

What gets written

• Bug and feature templates: impact, tickets, environment and version, repro steps, expected vs actual, logs, ruled out, and S1–S4 severity with a suggestion
• Two-way links: a Jira remote link, a Zendesk jira_<key> tag plus private note, or a ServiceNow work note
• Owner routing: on-call, then Jira component lead, then CODEOWNERS. Pings never use @channel or @here
• Customer PII is stripped; ticket ids, error codes and versions are kept