Email This Issue
📈 Marketplace❓ Support❤️ Feedback🏠 META-INF Apps
Email This Issue - for Jira Cloud
Email This Issue - for Jira Cloud
  • ⬇️Overview
  • Email This Issue - for Jira Cloud
  • Features
  • How Email This Issue Works
  • Secure the email channel with Email This Issue
  • Comparing Email This Issue and Jira Cloud
  • 📤Outgoing Emails
    • Outgoing emails overview
    • Manual emails
      • Configuring manual emails
      • Sending manual emails
    • Email notification schemes and email notifications
    • Workflow post functions
    • Advanced email configuration
    • Customizing email templates
    • Canned Responses (default messages)
    • Scope evaluation
  • 📥Incoming Emails (Mail Handlers)
    • Incoming emails overview
  • Mail handlers - adding / editing
    • General handler settings
    • Filtering
    • Finding issues
    • Setting up rules and actions in the actions editor
      • Adding/editing actions
      • Adding recipients to Request Participants
      • Creating an issue
      • Updating an issue
      • Setting field values
      • Adding comments
      • Sending auto-reply emails
      • Executing workflow transitions
      • Creating a customer
      • Using split regexp
      • Conditions
      • Approve request
      • Decline request
    • Maintaining email chains
    • Mail Handler New UI
  • Global Sender Address Filters
  • Attachment Filters
    • Regular Attachment Handling Deprecation
  • 🤓Administration
    • Outgoing Mail Connections
    • Alerting via Webhooks
      • Webhooks
        • Configuring Slack to receive alerts via webhooks
        • Configuring OpsGenie to Receive alerts via webhooks
        • Configuring Microsoft Teams to receive alerts via webhooks
      • Webhook execution logs
    • Mail Queue
    • Email Audit Log
    • Permissions
    • Recipient Restrictions
    • Incoming Mail Connections
    • Email Security
    • Incoming Mail Queue
    • Incoming Mail Log
    • OAuth2 Credentials
      • Enabling OAuth2 Authorization in your Google Account
      • Enabling OAuth2 Authorization in your Microsoft 365 Account
      • Troubleshooting guides for Microsoft OAuth2 Connections
        • How to fix "BAD User is authenticated but not connected" error​
        • How to fix "401 Unauthorized" error
        • How to fix "key expires_in " error
        • How to fix "Need admin approval" error
  • ☁️Server to Cloud Migration
    • 🛫Server to Cloud - Automatic Migration tool
      • Preparing for the migration
      • Doing the migration
      • Finalizing the migration in Cloud
      • Migration with unsupported Jira versions causes errors
    • Server to Cloud - Manual migration guide for Email This Issue
  • ❓FAQ
    • No recipients error in outgoing emails
    • How-to add custom macro to email Template?
    • Why cannot I select custom event types in notification?
    • How to configure the Email This Issue addon user in Jira Cloud?
    • I get an error: Could not create request on behalf of the sender
    • Why is the Incoming Mail Queue size limited?
    • Outgoing mail not sent - Read timeout error
    • Access restriction icon is not appearing when adding internal attachments via Email this Issue
  • 🌪️General
    • Release Notes
    • API
      • API for Velocity Context Objects - 1.7
      • API for Velocity Context Objects
    • Addon Pages
      • Integrity Check
      • Feedback and Support
    • Security Advisories
      • Email This Issue Security Advisory September 28, 2020
    • Appendix
      • Supported Time Zones
    • Integration of Glass Documentation
Powered by GitBook
On this page
  • General information
  • On-prem to Cloud Migration support
  • Configuration data
  • Operational data

Was this helpful?

  1. Server to Cloud Migration

Server to Cloud - Automatic Migration tool

PreviousHow to fix "Need admin approval" errorNextPreparing for the migration

Last updated 1 year ago

Was this helpful?

General information

The automatic migration path for Email This Issue is available since version 9.3.0 in On-prem versions (the Cloud version is released at the same time of this version). It can be used to plan and execute migrations in test and production environments alike.

Current limitations of the migration:

  • No filtering for project data is available. If you set it in the Jira Cloud Migration Assistant to only migrate certain projects, it will not be applicable to the Email This Issue configuration.

  • Email This Issue migration tool supports only full migration. All old data on Email this Issue Cloud side will be lost once the migration is done.

  • The migration of Mail Handlers is limited in its functionality. For more details see the section.

  • The Default event type will not be migrated, therefore this event type will be removed from the Notification events' Event Types list. If the Notification event was listening only on the Default event, the notification event will not be migrated at all.

  • Workflow post-function settings are not migrated at all.

The process of moving Email This Issue data from On-prem to Cloud instances can be divided to three main sections:

On-prem to Cloud Migration support

The below tables attempt to list the migration modes of Email This Issue features.

FULL means that all data is automatically migrated during the process and needs only a check-up from the user when it's done.

Configuration data

On-prem configuration
Cloud configuration
Migration mode

OAuth2 Credentials

OAuth2 Credentials

Outgoing Mail Connection

Outgoing Mail Connection

Incoming Mail Connection

Incoming Mail Connection

Next-Gen Mail Handler

Mail Handler

Template

Email Template

Webhook

Webhook

Notifications

Email Notification Schemes

Context

Manual Email Configuration

Context

Advanced Email Configuration

Manual Email Defaults

Manual Email Configuration

Canned Responses

Responses

Distribution Lists

Attachment Filters

General Configuration

Advanced Email Configuration

General Configuration

Manual Email Configuration

General Configuration

Permission Schemes

Workflow post-function

Workflow post-function

Operational data

Server configuration
Cloud configuration
Migration mode

Email log

Email Audit Log

Outgoing Mail Queue (Mail Generation Queue)

Outgoing Mail Queue

Incoming Mail Queue

Incoming Mail Queue

Incoming Mail Log

Incoming Log

CORRECTION REQUIRED means that the user should manually check and carry out additional configurations after the migration is done.

NOT SUPPORTED means that the features are not migrated at all. This is either due to them not being applicable to the Cloud platform or it is due to technological limitations.

FULL

CORRECTION REQUIRED

CORRECTION REQUIRED

CORRECTION REQUIRED

CORRECTION REQUIRED

FULL

FULL

CORRECTION REQUIRED

CORRECTION REQUIRED

CORRECTION REQUIRED

CORRECTION REQUIRED

NO SUCH CONFIGURATION

NOT SUPPORTED

NO SUCH CONFIGURATION

NOT SUPPORTED

CORRECTION REQUIRED

CORRECTION REQUIRED

FULL

NOT SUPPORTED

FULL

NOT SUPPORTED

NOT SUPPORTED

NOT SUPPORTED

☁️
🛫
🔧
⛔
✅
Finalize Migration in Cloud
Preparing Email This Issue for migration
Using the Cloud Migration Assistant, affectively doing the migration
Post-migration configurations
✅
🔧
🔧
🔧
🔧
✅
✅
🔧
🔧
🔧
🔧
❌
⛔
❌
⛔
🔧
🔧
✅
⛔
✅
⛔
⛔
⛔