File the Jira issuewithout leaving the app
The work shows up everywhere but Jira: a bug in your inbox, a request in a Slack thread, a broken state in the browser. Khint lets you select that text wherever it lives, hit one shortcut, and create, comment on, or move a Jira issue: no tab-switch, no re-typing, no losing the thought on the way to the tracker.
The tax isn't the ticket,
it's the trip to file it
A PO reads a hundred things a day in a hundred places. Almost none of them are in Jira. So the small, constant cost is the context switch: copy the line, find the Jira tab, click New issue, pick the project, paste, reword it so it makes sense, save. Done often enough, the friction wins: the thought gets a “I'll file it later” that never comes. Khint collapses that trip with its three pillars (Agents, Capture, and Memory) wired behind one palette, so the ticket gets filed from wherever you spotted the work.
From any window to Jira, in one shortcut
Filing tickets across a scattered morning without breaking flow.
Connect Atlassian once
On the MCP page, open the Atlassian card and paste your email, an API token, and your cloud domain. They go into your OS keychain: local-only, no Khint server involved. From then on the palette carries a JIRA section, and you can hide any row you never use so it shows just the actions you file.
Catch the work where you read it
A bug report in your inbox. A “can we also…” buried in a Slack thread. A broken state you spotted in the browser. Select the text right there: no copy into a Jira tab, no new window. Khint reads the selection from whatever app is in front of you.
Open the palette and shape the ticket
Hit Cmd+Shift+K. Pick your Create issue row and the selection runs through a saved Action first, so a rough note becomes a clear title, description, and acceptance criteria instead of a raw paste. No prompt yet? Type a description and press Generate; tighten it later with Improve.
File it: create, comment, or move
Create issue opens a new ticket in your project. Already have one? Add comment appends your note to an existing issue, and Change status moves it along: one issue per run, so each write is deliberate. The same shortcut covers all three without leaving the app you started in.
Keep the trail in Memory
Open a Memory session for the day and every issue you file is logged to it, with a compact running summary that rides along on the next Action. So the third ticket you create from a scattered morning already knows the context of the first two.
The JIRA rows in your palette
Connect Atlassian and these appear behind the shortcut: three writes, three reads.
Why not just keep a Jira tab open?
You can, and you'll still copy the line, find the tab, click through the new-issue form, and reword the paste by hand every time. Khint removes the round trip: the formatting Action is saved once and runs on every selection, Memorycarries the product context into each ticket automatically, and the issue is filed from the app you were already in. Because an Action only sees the text you select (plus the session summary you opted into) and the Jira call goes straight from your machine with your own token, an unreleased feature you're ticketing isn't sitting in a chat history. When the input is a meeting instead of a stray line, see meeting notes to Jira tickets.
Common questions
Which apps can I file a Jira issue from?
Any app where you can select text. Khint lives behind a global shortcut (Cmd+Shift+K), so the palette opens over your browser, your email client, a Slack window, a planning doc: wherever you happen to be reading. It grabs the text you have selected in the frontmost app, runs it through your AI Action, and the Jira rows file the result. You never switch to a browser tab for Jira just to capture a thought.
What can Khint actually do to a Jira issue?
Once you connect Atlassian, the palette gains a JIRA section with Create issue, Add comment, and Change status as write rows, plus Pull issue, Active sprint, and Search for reading. So from any app you can open a new ticket, append a comment to an existing one, or move a ticket's status. One issue per run, so every change is explicit and nothing is filed silently in the background.
Does it just dump my raw selection into the ticket?
Only if you want it to. The Create flow runs the text through a reusable Action first, so a rough bug note becomes a clean title, description, and acceptance criteria before it lands in Jira. If you keep a Memory session open, that Action also sees your compacted session context, so the ticket inherits the product area you have been working in rather than starting cold.
How do I connect Jira, and where do my credentials live?
On the MCP page, open the Atlassian card and enter your email, an API token, and your cloud domain. Those three values are stored in your operating system's keychain, not on Khint's servers: the Atlassian connection is local-only and PAT-based. You can hide any palette row you don't use from the same card, so your JIRA section shows only the actions you actually file.
Is my selected text sent anywhere I can't see?
An Action only ever sees the text you selected, plus the compacted summary of your active Memory session if you opted in. Memory sessions live in a local SQLite database on your Mac and are never synced to Khint's servers. The Jira call goes straight from your machine to your Atlassian cloud with your own token. Nothing about an unreleased feature leaks into a chat history.
File your next ticket where you found it
Free with 10 AI actions and 5 captures per day. No credit card. Connect Atlassian once, file from any app after.