Skip to content
Edmund
Integration

Route a thought to Jira

When a captured note is ready to become tracked work, send it to Jira as a properly formed issue. Title, description and issue type, filed in the right project. Cloud or Server, your call.

How it works

From a thought to a Jira issue

  1. 1
    Capture and let Edmund triage
    Type or dictate it. On-device AI reads it and files it into the right project.
  2. 2
    Tap Route, choose Jira
    It’s created in the project and issue type you set up, on Jira Cloud or your own Server / Data Center.
  3. 3
    Tidy the title and send
    Edit the title and body if you like, then it lands in Jira, linked back to the note.
Coming to the App Store
JiraEDM-204
Auto-stop swallows the final word of a dictation
When the mic cuts on silence the last word never reaches the field. Looks like the buffer flush races the stop.
BugBacklogvoice
Routed from Edmund · just now
Once it’s routed

Route it here.
Finish it in Jira.

Routing isn’t a one-way dump. A real issue appears in Jira, it stays linked to the note, and finishing it there flips the note to Done back in Edmund.

A new issue appears in Jira

The summary becomes the issue title and the full note travels across as clean Markdown, filed in the project and issue type you set up, on Jira Cloud or your own Server / Data Center.

JiraDone
Auto-stop swallows the final word of a dictation
Syncs
EdmundDone
Auto-stop swallows the final word of a dictation

Move the issue to a Done-category status in Jira and the note advances to Done, one direction only, and it never re-opens a note you’ve already closed.

What carries over

Everything the issue needs, already filled in.

Title
The note’s one-line summary becomes the issue title.
Description
The full note travels across as clean Markdown.
Project & issue type
Filed where you set it up, as the type you chose.
Two-way done
Move it to a Done-category status and the note marks Done.
Get started

Connect Jira in a minute

Connect Jira Cloud with one tap, or use an API token. Cloud takes a token plus your Atlassian email; Server and Data Center take a bearer PAT, no email. Pick whichever fits your setup.

How you connect
One-tap OAuthorAPI token
Coming to the App Store
  1. 1
    Connect or add a token
    In Settings → Integrations → Jira, tap Connect for Cloud, or paste an API token. Cloud: a token from id.atlassian.com and your Atlassian email. Server / DC: a personal access token, email left blank.
  2. 2
    Point it at your project
    Set the site URL and project key for each Edmund project you want to route.
  3. 3
    Route your first note
    It’s created in that project as the issue type you chose, linked back to the note.

Edmund only talks to Jira the moment you choose to route, never in the background. Revoke access any time from Settings, or from Atlassian.

New to routing? See connecting integrations for how it all fits together.

Not ready for a beta? Just get the nudge.

No TestFlight, no commitment. Leave your email and I’ll tell you the day Edmund lands on the App Store. Nothing else, ever.