OrgSpec for Jira support

OrgSpec for Jira generates a candidate OrgSpec from Jira project, board, sprint, component, and selected issue metadata.

It is not a Jira reporting dashboard, velocity tool, BI product, capacity planning tool, or Orgonaut integration.

Support contact

Public support contact:

• support@orgonaut.co
• /docs/orgspec/jira/support

What to include in a support request

Include:

• Jira site name or domain.
• App version if visible.
• Whether the app was installed from Marketplace or a private/development path.
• A screenshot or copy of the scan summary.
• Source Diagnostics if available.
• Validation result export if validation failed.
• Source contract export only if it is safe to share internally and account identifiers are acceptable for the support route.

Do not send:

• Issue descriptions.
• Comments.
• Attachments.
• Worklogs.
• Salary or compensation data.
• Production source contracts unless they are approved for support sharing.

Failed scan

Likely causes:

• The user is not logged into the intended Jira site.
• The app is not installed on the intended Jira site.
• The current Jira user cannot see projects or boards.
• App scopes changed and the app needs an install upgrade.
• Jira returned a permission or network error.

Recommended checks:

1. Confirm the intended Jira Cloud site is open.
2. Confirm the current user can see projects and boards in Jira.
3. Reopen Apps, then OrgSpec for Jira.
4. Run the scan again.
5. Review Source Diagnostics.

No visible projects

The app reads as the current Jira user. If the scan shows no projects, confirm that the user can open the expected Jira projects directly in Jira.

No boards

The app generates useful OrgSpec candidates from boards. If there are no boards:

• Confirm Jira Software is available on the site.
• Confirm the current user can see boards.
• Confirm the boards are associated with visible projects.

No sprints

Kanban and simple boards may not support sprint metadata. This is expected and should appear as a non-blocking diagnostic.

The app can still generate a candidate OrgSpec without sprint evidence, but it may not generate planning-cycle candidates for those boards.

Missing assignees

If no assignee evidence appears:

• Confirm sample issues have assignees.
• Confirm the current user can see issue assignee fields.
• Confirm the selected boards contain issue samples.

The app can still generate project and board candidates without assignee-derived placements.

Missing components

If no component evidence appears:

• Confirm projects use Jira components.
• Confirm sample issues have components assigned.

The app can still generate a candidate OrgSpec without component-derived capability candidates.

Simple boards

Simple or Kanban boards may not support sprint lookup. The app records this as a warning rather than failing the scan.

Validation failures

If OrgSpec validation fails:

1. Download the validation result JSON.
2. Download the mapping report Markdown.
3. Review any diagnostic messages.
4. Contact support with the validation result and a short description of the Jira structure scanned.

Export handling

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

Do not publish exports without reviewing and redacting them.

Known limits

• The current version samples up to 25 issues per board.
• The current version does not use persistent storage.
• The current version does not connect to Orgonaut.
• The current version does not read issue descriptions, comments, attachments, or worklogs.
• The current version does not read compensation or HRIS data.