Alert notification channel preferences reset after Jira Align upgrade

Answer the Core Questions

1. Does Jira Align preserve per‑alert notification channel preferences after a major upgrade?

Not guaranteed. Release notes for recent major releases explicitly warn that alert rule channel preferences may be reset during the migration process, and the behavior varies by version and subscription tier.

2. If preferences are reset, what is the recommended process to verify and restore them?

Follow a three‑step verification and restore routine (see Verification & Restoration Steps below).

3. Are there any admin‑level configurations that can enforce channel preferences across upgrades?

There is no documented, universal admin setting that locks channel preferences across upgrades. Some tiers expose a global notification policy, but it is not a standard feature across all environments. Verify whether your instance shows such a policy before relying on it.

Likely Explanation vs. Confirmed Facts

Likely Explanation: During a major version upgrade, Jira Align’s migration scripts may recreate alert rules from the database snapshot, defaulting channel settings to the platform’s standard values. This can happen even if the UI shows the channels as enabled because the underlying delivery pipeline was rebuilt.

Confirmed Facts:

• Release notes for v5.0+ mention a reset of alert rule channel preferences during upgrades.
• No universal admin‑level lock exists; only a few enterprise tiers expose a global notification policy.
• Verification must involve triggering an actual alert to confirm end‑to‑end delivery.

Verification & Restoration Steps

1. Pre‑Upgrade Baseline
   
   • Export all alert rules via the REST API (e.g., /api/v1/alert-rules) or take screenshots of the rule list and channel settings.
   • Document the channel configuration for each rule (In‑App, Email, Slack, etc.).
2. Post‑Upgrade Diff
   
   • After the upgrade completes, re‑export or re‑capture the alert rules.
   • Compare each rule’s channel list to the pre‑upgrade baseline. Note any that have reverted to default channels.
3. Functional Test
   
   • Create a temporary test rule that triggers on a predictable condition (e.g., a dummy issue status change).
   • Fire the rule and verify that notifications are received on every expected channel.
   • Use the audit logs or notification delivery reports to confirm that the channel pipeline is active.
4. Restore Affected Rules
   
   • For any rule that lost its channel configuration, re‑apply the correct channels via the UI or API.
   • Re‑export the rule to confirm the change persisted.
5. Document & Communicate
   
   • Keep a changelog of the rules that were restored.
   • If the reset occurs repeatedly or only for certain rule types, capture the pattern and open an issue with Atlassian Support, including the source and target version numbers.

Admin‑Level Enforcement (If Available)

Some enterprise tiers provide a Global Notification Policy under the Admin console. If present:

• Navigate to Admin > Global Settings > Notification Policy.
• Define default channels for each alert type.
• Enable the policy and verify that it overrides per‑rule settings during upgrades.
• Note: This feature is not available in all tiers; confirm its presence before configuring.

Missing Diagnostic Detail Needed

To tailor the recommendation more precisely, please provide:

• The exact source and target Jira Align versions you are upgrading between.
• The subscription tier (Standard, Enterprise, etc.) you are using.
• Which notification channels (In‑App, Email, Slack, Teams, etc.) you rely on most heavily.

With that information, we can confirm whether a global policy exists for your tier and whether the reset behavior applies to your specific channel types.