Work management

Jira

Issue tracking and project management

Overview Context types Tools Use cases Connection Security

Overview

Modus mines the Jira projects you select, including issue types and their field schemas, so agents understand your workflow rather than assuming a generic one.

What Modus reads

1Project (space)
2Issue
2Issue type
3Field

You select the level Modus is allowed to mine. Everything below it is discovered automatically; everything outside it is never touched.

4context types mined

5agent tool groups

1connection method

4security controls

Context types

Each object Modus mines produces typed context items, addressed by their position in the hierarchy. This is what an agent actually receives.

Project metadata & statistics
Selected projects, their configuration, and issue volume.
Issue metadata
Issues with their status, assignee, and content.
Issue type metadata & samples
Each issue type, its workflow, and representative examples.
Field metadata & statistics
Custom fields, their meaning, and how consistently they are filled in.

Example context item

jira_issue_type_metadata

REVBug

Workflow: Open → In Progress → In Review → Done
Required fields: Severity · Affected component
Custom field: Customer Impact (used on 78% of issues)
Volume: 1,204 issues in 90 days

Tools

Tools are granted per skill, never globally. Anything that changes state in Jira is marked as a write and stops for human approval.

Search issues (JQL)
Search and reconcile issues using JQL, count issues, and bulk-fetch results.
Read issues
Issues, comments, changelogs, worklogs, attachments, links, watchers, and votes.
Project & schema
Projects, components, versions, roles, fields, statuses, workflows, and issue types.
Users
Find users and groups and resolve assignability.
Create & update
Approval required
Create issues, comment, transition, assign, link, and edit — gated behind explicit approval.

Common use cases

Answer "what shipped this quarter" from real issue state, not a status doc.
Let a triage agent file an issue with the fields your workflow actually requires.
Connect a data quality complaint to the ticket already tracking it.

Connection method

Connect once. Modus stores credentials in a managed secret store, rotates what it can, and never asks an agent to handle them.

OAuth (managed)

Managed Atlassian OAuth, scoped to the projects the connected identity can reach.

Security & governance

Governance is applied once, at the layer every agent runs through, so it holds no matter which agent asks.

Metadata-first mining

Modus learns from structure and usage, not bulk data. Raw records stay in your environment; only the metadata needed to understand the system is stored.

Scoped selection

You choose exactly which schemas, folders, spaces, or boards Modus is allowed to see. Nothing outside the selection is ever mined.

Write approval

Actions that change state in the source system are marked as writes and require an explicit human confirmation before they run.

Group access by sensitivity

Map your identity groups to sensitivity tiers so each team only ever composes context at or below its clearance.

Put Jira to work.

Connect it in minutes and give every agent a governed understanding of what is inside, without moving a single row of data.

Book a demo