Use OrgSpec for Jira

OrgSpec for Jira generates a candidate machine-readable organisation specification from Jira work structures.

It uses Jira projects, boards, sprints, components, and selected issue metadata as evidence. It does not treat Jira as a perfect source of truth for formal organisational hierarchy.

Run a scan

1. Open Jira.
2. Open Apps.
3. Select OrgSpec for Jira.
4. Review the data boundary on the first screen.
5. Click Scan Jira.
6. Wait for the scan to complete.

The scan checks visible projects, boards, sprint metadata where available, and selected issue metadata.

Review the scan summary

The summary shows counts for:

• Projects.
• Boards.
• Scrum boards.
• Sprints.
• Issue samples.
• Assignee evidence.
• Component evidence.
• Warnings.

Counts are evidence, not guarantees. Low counts usually mean Jira has limited data for the current user or board type.

Review Source Diagnostics

Source Diagnostics explain whether evidence was:

• Present.
• Absent from Jira response.
• Blocked by permissions or API error.
• Blocked by board type.
• Dropped during normalization.

Use diagnostics to decide whether the generated OrgSpec needs manual review before use.

Review the generated OrgSpec

The generated OrgSpec preview summarizes candidate:

• People.
• Teams or work containers.
• Relationships.
• Capability candidates.
• Planning cycles.
• Missing data warnings.

The generated OrgSpec is a candidate model. Human review is required before using it for decisions.

Review validation

The validation status shows whether the generated OrgSpec conforms to the current OrgSpec schema.

A valid OrgSpec means the file is structurally valid. It does not mean every inferred team, placement, or relationship is organisationally true.

Review the mapping report

The mapping report explains how Jira evidence was mapped into OrgSpec.

Use it to check:

• Which Jira boards became team or delivery-stream candidates.
• Whether assignees produced placement evidence.
• Whether components produced capability candidates.
• Whether sprints produced planning cycles.
• Which mappings are high, medium, low, or unknown confidence.

Export files

The app can download:

• OrgSpec JSON.
• Mapping report Markdown.
• Jira source contract JSON.
• Validation result JSON.

Downloaded exports may contain Jira account identifiers. Treat exports as internal organisational data.

What the output is for

Use the output to:

• Establish a current-state baseline.
• Review how Jira work structures imply teams, ownership, and planning cycles.
• Identify missing or ambiguous organisational data.
• Create a portable OrgSpec document for review.
• Prepare for future scenario modelling outside the current app.

Do not use the output as an automatic restructuring recommendation.

Current limits

• No persistent storage.
• No Orgonaut integration.
• No billing.
• No scenario creation.
• No issue descriptions, comments, attachments, or worklogs.
• No compensation or HRIS data.
• Up to 25 issue samples per board in the current MVP.