What happens to Jira Automations when you change objects?

[mir_contact_stable_point_io]

If you’ve ever modified a custom field, workflow, or object in Jira, you’ve probably asked yourself:

👉 “Will this break my automations?”

The short answer is: it might — and often in ways you don’t expect.

🔍 The hidden impact of Jira changes

Jira automations are tightly connected to multiple elements:

• Custom fields
• Issue types
• Workflows
• Screens
• Permissions
• Assets / Objects (JSM)

When you change or remove one of these, automations can:

❌ Stop triggering
❌ Fail silently
❌ Use outdated values
❌ Produce incorrect results

💥 Real example

Imagine:

• You rename or delete a custom field
• This field is used in 5 automation rules

👉 Result:

• Rules may break
• Conditions fail
• Actions don’t execute properly

And the worst part?

👉 Jira doesn’t always warn you clearly.

🧠 Why this is risky

In large Jira instances:

• Dependencies are complex
• Automations are numerous
• Documentation is often incomplete

So a “small change” can have unexpected cascading effects.

✅ Best practices before making changes

Before modifying anything in Jira, it’s good to:

✔️ Identify all dependencies
✔️ Review automation rules using the object
✔️ Check workflows and screens
✔️ Test changes in a safe environment

🤔 But how do you find all dependencies?

This is where things get tricky.

Manually checking:

• automations
• workflows
• fields
• configurations

👉 can take hours (or days)

💡 Idea: visualize impact before changes

One approach I’ve been exploring is:

👉 impact analysis before applying changes

The goal:

• understand what will break
• see dependencies instantly
• avoid production issues

🔧 Example solution

I’ve been working on a tool that helps with this:

👉 It analyzes dependencies across:

• fields
• workflows
• automations
• objects

And shows the impact before you make changes.

If you're curious, here’s the plugin:
👉 https://marketplace.atlassian.com/apps/4251492671/impact-analysis-for-jira

🚀 Final thought

Jira is powerful, but also highly interconnected.

👉 The bigger your instance, the higher the risk.

So before your next change, ask yourself:

“Do I really know what this will impact?”

💬 Discussion

How do you currently manage impact analysis in Jira?

• Manual checks?
• Documentation?
• Scripts or tools?

Curious to hear your approach 👇