Step 1 - Choose the element type
Select the Jira object you want to analyze: Space, Custom Field, Work Item Type, Status (and other upcoming types).
Plugin Documentation
Impact Analysis for Jira - Complete Marketplace Guide
This page explains every step of the plugin, how to run an analysis, how to save it, and what actions to take before critical Jira changes.
Plugin purpose
Impact Analysis for Jira helps you predict the outcome of Jira changes (edit, delete, add) before execution. The plugin maps dependencies to reduce regressions and prevent unmanaged high-risk configuration changes.
What you get
Immediate visibility into impact across filters, boards, workflows, screens, work items, and automations.
When to use it
Before any Jira configuration change, especially deletions and renames.
Who it is for
Jira Admins, PMO teams, support/ops teams, and change governance owners.
Plugin workflow - 4 steps
Standard flow for every impact analysis.
Step 2 - Select the specific item
Use List or Analytics view to find the target item. In this step, you also get a global analytics view of Jira objects across your instance before selecting the exact element to change.
Step 3 - Choose the action
Pick the action to simulate (Edit, Delete, Add). The plugin then prepares the full impact analysis.
Step 4 - Review impact results
Review impacted areas (filters, boards, workflows, screens, automations), warnings, and required manual actions.
How to run an analysis
- Open Impact Analysis for Jira from Jira Apps.
- Select the element type (Space, Custom Field, Work Item Type, Status, etc.).
- In Step 2, review the global analytics for Jira objects in your instance, then select the target item.
- Choose the action (Edit, Delete, Add).
- Run impact analysis and wait for scan completion.
- Review impacted areas and warning messages.
- Decide pre-change actions (manual and automatic updates).
How to save an analysis
- On the result screen (Step 4), click Save Analysis.
- Confirm the success message (Analysis saved).
- Click Saved Analyses in the top bar.
- Find your analysis by name, element type, action, or user.
- Click Load Analysis to reopen a saved report.
- Use export (if enabled) to attach results to governance workflows.
Saved Analyses
Saved Analyses is your analysis library. It helps you keep a full history of impact reports, reload previous scans, and compare decisions before and after Jira changes.
- Open Saved Analyses from the top action bar.
- Search by element type, element name, action, date range, or user.
- Click Load Analysis to reopen any saved impact report.
- Use saved reports as governance evidence for approvals and audits.
Example: Delete a Work Item Type
Before deleting a Work Item Type, run an impact analysis to estimate the full blast radius across your Jira instance.
Check impacted Screens and Screen Schemes.
Identify Spaces/Projects currently using this type.
Count how many Work Items of this type still exist in the instance.
Review impacted Filters and subscriptions.
Review impacted Boards through board filters.
Review Automation Rules that read, create, or transition this type.
Add screenshots from impacted areas to your change request to support validation and rollback planning.
Automation prerequisite
If you want to measure the impact of an action on a Jira object, import/sync Automation data first, then choose the action.
Without Automation data, rule-level dependencies may be missing from the final report.
Action checklist before making changes
You can reuse this checklist as-is in your Marketplace listing or internal change runbook.
- Confirm the target item (name, ID, type, project/space)
- Check risk level (Low Impact / Impact / Critical Warning)
- List impacted objects: filters, boards, workflows, screens, automations
- Identify mandatory manual actions before changes
- Share findings with stakeholders (admin, ops, project owners)
- Save the analysis to the library before execution
- Execute the Jira change
- Reload a saved analysis to verify post-change status