SourcesPlans and work
Mithrandir + Jira
Connecting Jira gives every AI agent your company uses the history of its work: what was planned, what shipped and why it changed. Claude, ChatGPT, Copilot and Cursor answer with the issue behind them. Each person sees only what Jira already shows them, down to project permissions and issue security levels.
What it reads
What Mithrandir reads from Jira
- Projects, issues and their fields
- Comments, restricted ones included
- Assignees, reporters and status history
Access
The access rules that carry over
- An issue reaches the people who can browse its project.
- An issue with a security level reaches only that level's members.
- A comment restricted to a group or role reaches only the people in it who can also see the issue.
- A public project's open issues reach everyone at the company.
Setup
Set up in three steps
- 1
Your Jira admin approves the Mithrandir app once, or creates one read-only service account.
- 2
Your projects' issues and comments come in, and changes follow from then on.
- 3
People ask from the agent they already use and get answers from the issues they can see.
Examples
What your agents can now answer
- “Why was this feature pushed out of the last release?”
- “Which issues are blocking the migration, and who owns them?”
- “Has this bug been reported before, and how was it fixed?”
Questions
Jira and Mithrandir, answered
- Do issue security levels carry over?
- Yes. An issue with a security level reaches only the people Jira lets see that level, and a restricted comment only the group or role it names.
- Does it work with Jira Data Center?
- Yes. Jira Cloud and Jira Data Center are both supported.
- Can agents change issues in Jira?
- No. Jira access is read-only.
Last updated 25 October 2026 · Mert Uzun, co-founder