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

Was this helpful?

  1. Server to Cloud Migration
  2. Server to Cloud - Automatic Migration tool

Finalizing the migration in Cloud

PreviousDoing the migrationNextMigration with unsupported Jira versions causes errors

Last updated 1 year ago

Was this helpful?

As previously stated there are certain configurations that the migration tool cannot move from the On-prem version of the application to the Cloud version.

These need to be finalized manually by the user, and this document aims to share the details on what needs to be done.

1. Authorizing OAuth2 Outgoing Mail Connections

If any of the migrated Outgoing Mail Connections uses the OAuth2 method for authentication, they should be authorized before usage.

  • Before you authorize replace the redirect URI (The value is always the following: ) at your email provider. For more details visit the documentation depending on your provider or .

  • To authorize, open the connection, then click on Authorization and follow the steps on your email provider site. You can find the connecting documentation .

2. Authorizing OAuth2 Incoming Mail Connections

If any of the migrated Incoming Mail Connections uses the OAuth2 method for authentication, they should be authorized before usage.

3. Correcting the mail handler and adding actions

The migrated mail handlers do not contain any actions, due to severe differences in handler functions between the Email This Issue Cloud and On-premise instances. They are, therefore, created as a basic Cloud mail handler and they are using the migrated Incoming Mail Connections.

The Cloud mail handlers have four tabs:

  • General handler settings

  • Filters

  • Find issue

  • Rules and actions

The General handler settings are by default filled with values during the migration, all they need is a check from the administrator.

Filter Emails comparison

The below table shows the email filtering options both in On-premise and in Cloud versions:

On-premise option
Cloud option
Migration status

Bulk emails

Filter out bulk emails

FULL MIGRATION

Delivery status notification emails

Filter out delivery status notifications

FULL MIGRATION

Auto-submitted

Filter out auto-reply emails

FULL MIGRATION

Large emails

-

NOT AVAILABLE

Emails sent from this Jira system

Filter out emails sent from Jira

FULL MIGRATION

Emails sent from other Jira system

Filter out emails sent from Jira

FULL MIGRATION

Emails sent from unknown addresses

-

NOT AVAILABLE

Emails by recipient address

Accept email if any recipient equals...

NEEDS MANUAL SETUP

Emails by email attribute

-

NOT AVAILABLE

Emails by sender address

NEEDS MANUAL SETUP

Find Issues for Email

The below table shows the email filtering options both in On-premise and in Cloud versions

On-premise option
Cloud option
Migration status

Find issues by issues key appearing in the email subject

Default issue lookup (no option for enabling/disabling)

FULL MIGRATION

Find issues by references in email headers

Enable issue lookup by mail headers

FULL MIGRATION

Find issue by JQL

Enable issue lookup by JQL

JQL NEEDS TO BE EDITED MANUALLY

4. Checking Email Templates

Depending on the complexity of the migrated templates they may not be working correctly. Please test each template and make the necessary corrections before using them.

  1. Check all Jira related identifiers: - Project key / ID - Issue type / ID - Field / custom field ID - User name / ID - Group name / ID - Roles

5. Check Advanced Email Configuration

  • Check that the correct Outgoing Mail Connection is selected

  • Correct the JQL filter if needed

  • Make sure that your Reply/Forward template is correct (other template options may be found in the Manual Email Defaults)

  • Check the order field

6. Check Recipients

Places where the Recipients are used:

  • Manual Email Configuration recipients

  • Notification Event recipients

  • Recipient Restrictions

Recipients in the application may take up different input forms. These can be:

  • Users

  • Email addresses

  • Roles

  • Groups

  • Custom fields

  • Other special fields (eg. Reporter, Assignee, Watchers, etc)

If for some reason a value is not migrated by Jira, it cannot be resolved by Email This Issue. You have to check recipients in the settings and fix them manually after the migration process if needed.

Some examples for why the values would not be migrated:

  • You are migrating selected projects and project-related users. If you refer to a Role as a recipient, but the project does not have any members in that role, then the role is not migrated and will be missing from the recipients.

  • You are migrating selected projects and project-related groups. If you refer to a Group as a recipient, but the project does not have any members in that group, then the group is not migrated and will be missing from the recipients.

  • If a custom field is not used on any issues, it is not migrated.

7. Manual Email Configuration

If you have a Manual Email Configuration migrated, correct the JQL filter if needed.

8. Check Email Notification details

If you have a Notification configured to use any of the following attachment settings:

  • Added in the last operation or

  • Attachments from attachment selector field

they have been migrated as None since these options are not availbe in the Cloud. If you have a different option selected, please update this part of the configuration.

Also correct the JQL filter if needed.

Notification Event mappings

The list of supported events are different on the On-Prem and on the Cloud versions of our product. Here you can see a comparison of supported events and how they are mapped:

Server
Cloud

Default Event

Not Supported

Issue Archived

Not Supported

Issue Restored

Not Supported

Request Created

Issue Created

Request Updated

Issue Updated

Request Resolved

Issue Resolved

Request Reopened

Issue Reopened

Customer Visible Status Changed

Not Supported

9. Disable data migration to your cloud instance in Email This Issue

When you are done with finalizing your settings on your Cloud instance, disable data migration in Email This Issue Administration - Migration options.

10. Workflow post-function

Before you authorize replace the redirect URI (The value is always the following: ) at your email provider. For more details visit the documentation depending on your provider or .

To authorize, open the connection, then click on Authorization and follow the steps on your email provider site. You can find the connecting documentation .

You are required to open each Mail Handler, and build up the complete Rules and actions secion from scratch manually. You can find the documentation on how to do so .

Check out the differences between Cloud and on-premise velocity macros on the below document pages: - On-premise - Cloud

This step is necessary if the migration contained any Advanced Email Configurations (It is a mix of the General Configuration and the Context on the On-prem platforms). For more information, please refer to the Advanced Email Configuration .

As the workflow postfunctions are not migrated at all please follow the manual migrations steps detailed at if you have any on the server side.

☁️
🛫
https://jeti.addon.meta-inf.hu/admin/oauth2/callback
Google
Microsoft
here
here
documentation
documentation
documentation
Migrating Post Functions
Sender email address filters
https://jeti.addon.meta-inf.hu/admin/oauth2/callback
Google
Microsoft
here
Authorizing an Outgoing Mail Connection
Authorizing an Incoming Mail Connection
Editing templates on the Cloud