Overview
Self-hosted Jira Data Center or Server. Modus mines each project you select and keeps that context current.
What Modus reads
- 1Project
- 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.
6context types mined
4agent tool groups
1connection method
5security 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
A Jira project visible to the service account.
Project statistics
A Jira project visible to the service account.
Issue metadata
A Jira issue within a selected project.
Issue Type metadata
An issue type configured for a selected Jira project, with its workflow statuses.
Issue Type samples
An issue type configured for a selected Jira project, with its workflow statuses.
Field metadata
A field available on a Jira issue type, with its schema and create/edit requirements.
Common use cases
- 01
Answer where work stands from the Jira (On-Prem) item, not from a status meeting.
- 02
Let an agent update work only when a person approves the write.
Connection method
Connect once. Modus stores credentials in a managed secret store, rotates what it can, and never asks an agent to handle them.
Username & password
A dedicated user and password. Prefer a read-only principal wherever the source allows it.
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.
Data classification
Sampled values are scanned for PII, financial, health, credential, and government-ID patterns, then classified as Sensitive, Flagged, or Non-sensitive. Your own overrides win over the defaults.
Group access by sensitivity
Map your identity groups to sensitivity tiers so each team only ever composes context at or below its clearance.
Read-only by default
Mining runs on a read-only credential. Any tool that writes back is a separate, explicitly granted action.