To Product Updates Hub
Upcoming Atlassian deprecation affecting Script Listeners
Reece Smith
27 November 2025
Read in 2 min
Atlassian is deprecating the old event model and transitioning to a new Forge event model. This may cause your Script Listeners to stop working. Follow these steps to keep your Jira running smoothly.
Atlassian is deprecating the old event model and transitioning to a Forge event model. This may cause some of your Script Listeners in ScriptRunner for Jira Cloud to stop working.
Follow our guide below to discover which of your scripts (if any!) are affected, and how you can update them to keep your Jira instance running smoothly.
What is happening?
As part of Atlassian’s continued platform enhancements to transition from Connect to Forge, there is an upcoming deprecation of the old events model that will impact Script Listeners in ScriptRunner for Jira Cloud.
Atlassian is deprecating the old event model and all apps must now transition to the new Forge event model. The new model has a different structure and does not include all properties that were previously available on Connect.
Your Deprecation Report has been updated to help you identify and update any Script Listeners which are using the old properties on your instance(s).
The deadline for updating affected Script Listeners is 31 January 2026: any Script Listeners using the old event model will stop working after this date.
What should I do?
- Check your Deprecation Report. We’ve prepared a report highlighting the scripts that require attention.
- Update any affected scripts as soon as possible. Replace the deprecated event with the new Forge event using this guide.
- Use the new Forge event model when you’re writing new scripts.
If you have any questions or need some help, you can raise a ticket with our support team.