Overview
ChangeSafe analyzes Jira configuration and usage without modifying fields, issues, workflows, screens, filters, or dashboards.
Risk levels are based on supported dependency signals and stored-value evidence found in the connected Jira site.
Evaluate rename, hide, remove/delete, context, and option changes before carrying them out in Jira.
ChangeSafe is built on Atlassian Forge and is designed without an external customer-data database or external application server.
Installation
ChangeSafe is installed from the Atlassian Marketplace by a Jira administrator. Follow the Marketplace installation flow, review the requested read-only Jira permissions, and approve the installation.
After installation, open ChangeSafe from Jira administration. Access is intended for Jira administrators because the app analyzes administrative configuration and protected site-level information.
Getting started
- Open ChangeSafe for Jira from Jira administration.
- Choose or search for the custom field you want to review.
- Open the field analysis to inspect risk, dependencies, and stored issue-value usage.
- Select the exact change you are considering under Planned action.
- Review the decision, dependencies, Automation attestation, and evidence before making any Jira change.
Impact analysis
The Impact map summarizes how a field is used across supported Jira configuration and stored issue data. Depending on what exists on the site, the analysis may include:
- Field contexts and configuration
- Screens and screen tabs
- Projects and project associations
- Saved filters and dashboards
- Workflow-related references supported by the app
- Stored issue values for the selected custom field
ChangeSafe combines these signals into a risk level intended to help prioritize review. A risk level is decision support, not a guarantee that every possible Jira or third-party dependency has been detected.
Planned actions
ChangeSafe currently supports analysis of these planned custom-field actions:
- Rename field — assess references that may depend on the field name or identity.
- Hide field — review usage and dependencies before hiding the field from supported configuration.
- Remove or delete — apply the strictest checks, including stored issue-value evidence where available.
- Change context — review where the field is configured and which projects or issues may be affected.
- Change options — review field usage before changing option configuration.
Dependencies
The Dependencies workspace groups supported Jira references found for the selected field. Review each dependency before carrying out the planned change.
Because Jira sites can include apps, scripts, manual procedures, integrations, or configurations outside the APIs available to ChangeSafe, administrators should also consider organization-specific dependencies that may not be programmatically visible.
Jira Automation review
ChangeSafe uses an explicit administrator attestation for Jira Automation review. This is intentional: Jira Automation rule management is not exposed to ChangeSafe through a supported Forge/OAuth API that would allow the app to claim a complete automatic scan.
Before a clear planned-action result is treated as fully reviewed, the administrator should inspect relevant Jira Automation rules and attest that the field has been reviewed there.
Reports and evidence
ChangeSafe can produce read-only decision summaries and evidence based on the analysis shown in the app. Evidence is intended for peer review, change planning, governance, and audit support.
Reports should be interpreted together with Jira's current configuration and any organization-specific procedures. They do not replace an administrator's final review.
Trial and subscription access
ChangeSafe is a commercial Atlassian Marketplace app.
- Trial: full ChangeSafe functionality is available during an active Marketplace evaluation.
- Active subscription: full functionality remains available while the Marketplace license is active.
- Inactive subscription: ChangeSafe may remain accessible in a reduced state, but premium field-impact analysis is disabled until a valid trial or subscription is active.
Billing, entitlement, trial status, and subscription lifecycle are managed through Atlassian Marketplace.
Permissions and security
ChangeSafe requests read-only Jira scopes required to inspect custom fields, field configuration, screens, projects, filters, dashboards, workflows, groups, roles, users, and issue-value usage.
ChangeSafe does not request Jira configuration write permissions for its analysis functionality. Protected site-level analysis also verifies appropriate Jira administrative permission before app-authorized reads are used.
Important limitations
- ChangeSafe is a pre-change analysis tool, not an automatic change executor.
- Risk levels are based on supported evidence visible through Jira/Forge APIs and the app's analysis rules.
- Third-party apps, scripts, external integrations, undocumented dependencies, or manual processes may require separate review.
- Jira Automation should be reviewed manually and attested in ChangeSafe where applicable.
- Always validate important changes using your organization's change-management and backup/recovery procedures.
Support
For installation help, licensing questions, troubleshooting, or product support:
Tennex Digital
Email: support.changesafe@tennexdigital.com
Hours of operation: Monday–Friday, 09:00–17:00 Pakistan Standard Time (PKT / UTC+5). Saturday and Sunday: Closed. Initial response target: within 1 business day.