HELP CENTER · OFFBOARDING AUDITOR
Support that keeps work moving.
Get help with Offboarding Auditor for Jira, report a security concern, or ask about personal-data handling.
What we can help with
Support covers the documented Jira assignee/reporter scope.
- Installation, upgrade and access
- Inactive-account scan failures
- Incorrect or missing assignee/reporter dependency findings
- History, coverage and CSV/JSON audit exports
- Product defects, security and privacy questions
Prepare your request
Provide enough information to reproduce without exposing secrets.
- Jira Cloud site identifier or URL, where appropriate
- Approximate incident time and timezone
- Expected versus actual behavior
- Reproduction steps and affected role
- Redacted screenshots or test data
- App/release version if visible
Do not send passwords, Atlassian API tokens, OAuth/client secrets, Authorization headers, session cookies, browser authentication state, or private keys.
Severity guidance
Critical: data exposure or a critical outage. High: major production impact. Normal: partial degradation. Low: how-to or feature requests. Impact classifications are not a contractual SLA.
Current product boundary
Only Jira issue assignee and reporter dependencies are currently supported. Project and component ownership, filters, dashboards, automations, workflows and Confluence ownership are outside current coverage.