Thirty comments deep,one decision buried inside
Every product team has that ticket: weeks of comments, positions reversed twice, legal weighing in on comment 19, and nobody sure what was actually decided. Khint turns the whole thread into a short decision summary with one keyboard shortcut: select the discussion on the ticket page, run a saved AI action, and post the decision back as the comment that finally ends the argument.
The decision is in there,
but nobody wants to re-read for it
Long comment threads are where decisions go to hide. The outcome exists (somewhere between the first proposal, the counter-argument, and the message where someone finally talked to legal), but extracting it means re-reading the whole argument, and whoever does that becomes the team's unofficial court reporter. So the thread stays ambiguous, the same debate reopens in refinement, and new joiners ask the question comment 24 already answered. Khint makes the court-reporter job a saved prompt instead of an afternoon: Agentshold your “distill the decision” action behind one shortcut, Memorycarries the ticket's context so the summary resolves “the export” to the right feature, and the same palette writes the verdict back to Jira so the thread ends with an answer.
From noisy thread to posted decision, step by step
A contested ticket, three reversals, and a refinement session tomorrow that needs to know where it landed.
Save a “Distill the decision” Action once
In the Action editor, describe the job in one line: read a ticket discussion and extract the decision, the rationale, any scope change, and what is still open with an owner. Press Generate and Khint drafts the prompt; Improve refines it later as you see real threads. Give it a shortcut if contested tickets are a weekly event for you.
Open a session and pull the ticket's frame
Start a Memorysession named for the topic: “Export permissions”. With Atlassian connected on the MCP page, run Pull issuefrom the palette (Khint lists your recent issues so you pick instead of typing a key) and the ticket's summary, status, and description land in the session. Actions that opted into session context now know which ticket the thread belongs to.
Select the thread where it lives
On the ticket page, select the whole comment thread: the back-and-forth, the reversals, the “actually, legal said” three weeks in. Hit Cmd+Shift+K and run your Action. No copying into a chatbot tab, no re-explaining what the ticket is about: the selection is the input, and the session context fills in the rest.
Read the decision, not the argument
The result is a short, labeled summary: what was decided, why, what changed in the ticket's scope along the way, and what is still open with a name attached. It also lands on your clipboard, so it is ready to travel: into the ticket, into a status update, or into the refinement session where someone asks “wait, what did we decide on this one?”
Post it back so the thread can stop
From the palette, run Add comment: pick the ticket from your recent issues, paste the summary as the body, and confirm after the preview. The decision is now the last word on the thread, where the next reader looks first. If the outcome moved the ticket forward, Change status sits right below it in the same palette, and every write is logged into your Memory session.
Eighteen comments in, four sentences out
What a saved “Distill the decision” Action might make of a real permissions debate. The structure lives in your prompt.
anna: could gate the export behind the new permission, but legal wants it per-workspace · tomas: per-workspace breaks the mobile client, see AUTH-311 · anna: then we're blocked? · priya: talked to legal, per-user is fine if access is logged · tomas: ok, but that changes the scope of this ticket · mark: +1, and who owns the log retention setting?
Decision: ship the export behind a per-user permission with access logging, per legal's confirmation (Priya, May 14). Rationale: workspace-level gating breaks the mobile client (AUTH-311). Scope change: this ticket now covers the permission check and the access log; the workspace setting is out. Still open: retention period for the access log; Priya to confirm with legal by Friday.
Notice what the summary keeps that a casual skim loses: the date legal confirmed, the cross-ticket reference that killed the first option, the fact that the ticket's scope quietly changed mid-thread, and the one question that still has no answer, with a name and a deadline attached. That last part is what makes the posted comment useful rather than decorative: the thread doesn't just get a recap, it gets an owner for what remains. And because the format is your prompt, a team that runs decision logs can require the same four labels on every contested ticket.
Why not just paste the thread into a chatbot?
You can, and the first time it works fine. The tenth time, you are re-typing what the ticket is about, re-explaining the format you want, and hand-carrying the answer back into Jira: three tabs for a job that should be one keystroke. Khint collapses each of those: the format is saved in the Action, the ticket's frame comes from the Memory sessionyou pulled it into, and the round trip back to Jira is the palette's own Add comment, preview and confirm included. The habit also composes with the rest of your Jira work: find the noisy tickets in the first place with plain-English Jira search, file what the decision spawns with write to Jira from any app, and keep the tickets themselves sharp with AI ticket quality checks.
Common questions
Does Khint pull the comments out of Jira for me?
The comment thread itself you grab where it lives: Khint works on any text you can select, so you select the discussion right on the ticket page in your browser, hit Cmd+Shift+K, and run your action on it. What Khint does pull for you is the ticket's frame: with Atlassian connected, the palette's Pull issue command brings the ticket's summary, status, assignee, and description into your active Memory session, so the action summarizing the thread knows which ticket and which feature the argument is about.
How does the decision get back into Jira?
From the same palette, run Add comment. Khint lists your 15 most recently updated issues (with a "Type another key…" fallback for anything else), you pick the ticket, paste the distilled summary as the body, and Khint shows a preview behind an explicit confirm button. Nothing is posted until you click it. The posted comment is also logged into your active Memory session, so your running context records that the decision went out.
What does the distilled summary actually look like?
Whatever your prompt says it should. A useful shape is four labeled parts: the decision, the rationale, what changed in scope, and what is still open with an owner. You don't have to write that prompt by hand: in the Action editor, describe the job in one line and press Generate, then press Improve later when you see real outputs, for example to make it always name who committed to what.
Is the discussion I select shared anywhere?
An action only ever sees the text you selected, plus, if you opted in for that action, the compacted summary of your active Memory session. Memory sessions live in a local database on your machine, and the input and output text of your history stay local too. Each action also has an opt-in redaction setting that replaces emails, phone numbers, and similar personal data with placeholders before the text is sent to the model.
End the thread with an answer
Free with 10 AI actions and 5 captures per day. No credit card. The next contested ticket gets a decision comment, not a comment 32.