...
JQL Expression
Jira Filter - We don’t support the Jira Filter option in Cloud, and will automatically migrate from Jira Filter to per notification JQL notification
Custom Event Triggers - Atlassian Cloud does not allow apps to see Custom Events in Workflow Post Functions. This means that we do not support migrating Notifications with a Custom Event Trigger to NAFJ Cloud.
CRON Triggers - Because the on-premise and Cloud versions use different scheduler libraries, they are not perfectly compatible with one another. There is no way to make a perfect translation from one to the other. We will do a best effort on migration, but you may need to fix broken cron expressions.
Executing User - The Cloud version of NAFJ will perform all actions as its own user. If you have highly secured data which third party apps normally can’t access, you would need to grant us access for Notifications to work post migration.
Recipients
Component Lead - We don’t support this recipient at this time in Cloud
Advanced Notification Settings
Minimum issues to trigger notification - We don’t support this in Cloud at this time
Maximum times an issue can trigger a notification - We don’t support this in Cloud at this time
Sender email address - We don’t support this in Cloud at this time
Additional Send Hooks - We don’t support this in Cloud at this time
NAFJ Specific Custom Fields
Template for Notification - We will not support this field in Cloud, and as such, will not migrate it
Recipients to Notify - We will not support this field in Cloud, and as such, will not migrate it
Templates
Block Types
Loop Blocks - We don’t support this in Cloud at this time
...