ChangeSafe for Jira Documentation

1. Overview

ChangeSafe for Jira helps Jira administrators assess what a custom-field change could affect before they modify production Jira configuration.

2. What ChangeSafe does

ChangeSafe analyzes supported custom fields, field contexts, field configurations, screens, screen tabs, projects, project categories where applicable, saved filters and JQL references, dashboards, workflows, stored issue-value usage, dependencies and supporting evidence.

3. Supported planned actions

ChangeSafe can assess a planned rename, hide, removal or deletion, context change, or option change for a custom field. It evaluates these actions but does not execute them.

4. Getting started

1. Install ChangeSafe for Jira.
2. Open ChangeSafe from Jira.
3. Select a custom field.
4. Review the Impact Map.
5. Select the planned action.
6. Review risks, signals and blockers.
7. Inspect supported dependencies.
8. Complete Jira Automation attestation where required.
9. Review or save supporting evidence.
10. After appropriate review, make the actual change separately in Jira.

5. Impact Map

The Impact Map gives administrators a consolidated view of supported dependencies and usage before making a change.

6. Stored issue-value analysis

ChangeSafe can determine whether a selected field has stored Jira issue values and may present approximate usage information as supporting evidence.

7. Planned-action analysis

For a supported planned action, ChangeSafe presents a risk assessment, relevant signals, blockers and recommended review actions. This analysis supports administrator judgment; it does not guarantee zero impact.

8. Dependencies

Supported dependency analysis may include screens, contexts, projects, filters, dashboards and workflows, subject to the information exposed through supported Jira and Forge APIs.

9. Jira Automation attestation

Jira Automation cannot necessarily be fully inspected using all supported Forge and Jira APIs. Where required, ChangeSafe asks the administrator to confirm or attest that relevant Automation rules have been reviewed.

10. Reports and evidence

ChangeSafe can produce evidence and decision summaries to support an administrator's change review and governance process.

11. Permissions and security

ChangeSafe uses a read-only, least-privilege Atlassian Forge architecture. Protected analysis verifies appropriate Jira administrative permission before protected app-authorized reads. ChangeSafe requests no Jira configuration write scopes and requires no customer Atlassian password, Personal Access Token or API token.

12. Data handling

Processing occurs using Atlassian Jira and Forge services and, where applicable, the browser. ChangeSafe maintains no external customer-data database, operates no external application server for its core functionality, is designed without external customer-data egress, and uses no third-party analytics or telemetry within the app.

13. Subscription

ChangeSafe is intended as a Paid via Atlassian Marketplace app. Pricing and billing are handled through Atlassian Marketplace when publicly available.

14. Limitations

• ChangeSafe is advisory and read-only.
• It does not execute configuration changes.
• Supported Jira APIs determine which dependencies can be inspected.
• Administrators remain responsible for final review and change execution.
• Jira Automation may require administrator attestation.

15. Support

Visit ChangeSafe Support or email support.changesafe@tennexdigital.com.

16. Security

Read the ChangeSafe Security Policy or email security.changesafe@tennexdigital.com.

17. Privacy

Read the ChangeSafe Privacy Policy.