Migrating to NAFJ Cloud

Notification Assistant for Jira will support migration to Notification Assistant for Jira Cloud via JCMA. We expect the beta release to be available in February 2022.

What won’t be migrated

  • 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

  • Customer 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.

  • 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

    • Project Lead - We don’t support this recipient at this time in Cloud

    • Component Lead - We don’t support this recipient at this time in Cloud

    • CC Email Address - 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

      • Look Blocks - We don’t support this in Cloud at this time