Why Jira + dassi
Jira is already where the work happens. dassi adds the missing layer: it can read what’s on the page and then take actions (draft, classify, fill, log, summarize) without you rebuilding context in a chat box.
What to automate in Jira
- Keyboard navigation for issue lists: Add safe J/K navigation across lists and queues so triage is faster.
- Ticket context summaries: Summarize long ticket histories into current status, decisions, and next steps.
- Meeting prep from tickets: Generate agenda and talking points from linked issues before sprint ceremonies.
Quick start
- Open Jira in Chrome.
- Open the dassi sidebar.
- Start with a safe workflow: summarize → propose → draft → review → act.
Prompt recipes (copy/paste)
- “Add J/K navigation for this list and Enter to open the selected row.” (from Keyboard Shortcuts for Any Web App)
- “Bind Shift+R to open review notes, but never trigger Delete.” (from Keyboard Shortcuts for Any Web App)
- “Build a prep brief for this meeting: attendee backgrounds + recent threads.” (from Meeting Prep Panel Injected Into Calendar Events)
- “Pull last touchpoints from Salesforce and summarize them.” (from Meeting Prep Panel Injected Into Calendar Events)
- “Summarize what’s on screen and propose next actions.”
- “Do the safe part first (draft / label / preview), then ask me before any irreversible action.”
- “Turn this page into a clean checklist I can follow.”
Safety checklist
- Tell dassi: “Never submit/send without confirmation.”
- If the page contains sensitive data, ask for redaction or aggregated outputs (totals-only, no PII).
- Prefer reversible actions first (drafting, labeling, notes) before destructive ones.