Customers want an easier way of updating A4J rules when something changes on JIRA.

Current scenario:

• Customer have removed a link type from JIRA;
• Rules are still referencing the old link type and are failing when trying to run.
• The current way of fixing that is manually removing the link type.
• Customer have a lot of rules that needs to be updated and they wouldn't like doing that manually for all of them.

As per Daniel's comments:

The ideal would be to have an automatic service that runs every specific amount of time and helps updating rules in case of changes in JIRA.

There are several components that we need to consider (issue links are involved):
Triggers:

• Link deleted,
• Issue linked

Conditions:

• Related issues condition

Branch:

• for linked issues

Actions

• Delete issue links
• Link issue

Also components that could have custom JQL might be also affected (depending on user configuration).

Also when link type is deleted from Jira, user is asked whether to replace link type or to delete links - so there is space to discuss how smart our feature could be (remove or replace). For components with custom JQL we would need to  provide some lexical analysis to check if valid link types are used. It looks tough.

Just thinking loudly now: maybe some kind of recurring health-check, where we could add some routines ?

IMHO it is not as simple as bugfix, so we need to involve project management forces.