Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

Use Case

Follow the below step-by-step guide if you need to import whole email configurations into a system which does not have any email settings set up yet.
This could be the case when you need to migrate from your test environment to your production environment for example.

Prerequisites

It is a prerequisite that you have all projects, issue types, fields etc. already created in Jira before starting the Email This Issue Restore process. Everything you would like to set in Email This Issue has to be present before start the backup, please make sure to check these beforehand.

Jira elemek esetében az alábbi keresési feltételeknek kell megfelelni:

  • Projektnél: Név és project key egyezés kell
  • Issue Type/Request Type esetében a névnek kell ugyanannak lennie, és a projektben elérhetőnek kell lennie
  • A Field -eknél név és field type egyezés kell
  • Project role esetében a névnek kell megegyeznie
  • Issue Link Type esetében a névnek kell egyeznie
  • Group esetében a névnek kell egyeznie
  • User esetében a key alapján keresek (ezt még meg kell beszéljem Tibivel)

JETI elemek esetében az alábbiaknak kell megfeleni:

  • Template: Ezt vagy beimportálja, vagy név alapján találom meg
  • SMTP connection: Vagy beimportálja vagy név alapján találom meg.
  • Mail Account: Vagy beimportálja, vagy név alapján találom meg.

Step-by-Step

Generally speaking, there are four phases of a Backup/Restore process:

I. Creating a backup JSON file

II. Uploading the backup file to your new environment

III. Running the restore process

IV. Import results


We will go into details of the above steps in the following pages. If you follow them correctly, you should be able to carry out a backup of an old system and import all its Email This Issue settings into your new, empty Jira instance.

I. Creating a backup JSON file

To create a backup JSON file in the system from which you want to export your configurations, you will need to carry out the following steps:

  1. Navigate to Email This Issue - Administration -Backup/Restore.
  2. Click on Backup (next to Add file) and optionally fill the "Description of the export" field,  then press the Create button under the description field.
  3. Download the JSON file by clicking on the three dots at the end of the row and click on Download. Please note that the backup JSON file is by default stored at <Jira Home Directory>\data\emailissue\.


On this page

Detailed documentation

Backup and Restore Administration

II. Uploading the backup file to your new environment

To restore your current settings on the same- or on another Jira server instance you will have to upload a JSON file:

  1. Navigate to Email This Issue - Administration - Backup/Restore.

  2. Click on Add file then click on Browse.

  3. Select the JSON file you wish to restore then click Upload (or drag and drop the downloaded file in your browser).

  4. The file is now listed in a table below and can be used to restore your settings.



III. Running the restore process

After uploading the JSON file you can now start the restore process:

  1. Click on the three dots at the end of an uploaded item
  2. Click on Restore

The restore configuration has four stages:

  1. Entity selection

  2. Conflict resolution

  3. Overview

  4. Import results

  1. In the Entity selection, you can select which parts of your configuration you would like to import into your server instance. In this case, we would like to import everything, so we will need to select everything as shown below.

    The entities are presented with drop-down menus and are marked with a grey highlight, while the rows without any highlights are entity items.

    The entity items can be one of the following types:

    • Name of an entity (e.g.: the name of a template)
    • A Project and/or an Issue type can be selected within the entity, in which case it is presented as <Project name>; <IssueType name>
    • A Project and/or an Issue type can be selected within the entity, in which case it is presented as <Project name>; <IssueType name>; <JQL filter>

  2. After selecting the entities to be imported, click on Conflict resolution to proceed with the process.



  3. During the import, there could be conflicts regarding the items you wish to restore, but in this case, because we are restoring data in a blank system, there are none. Click on Create new to:

    1. click on the Insert imported parameters button on the right side of the drop-down menu to import the original names of the entities:



    2. add a scope to the imported entity (such as project/issue type/JQL setting):


  4. After creating the new entities, click on Check to see if the resolutions have been successful. If all the conflicts are resolved, the overview page is displayed and you may proceed with the restore process by clicking on Confirm.



IV. Import results

  1. After clicking on Confirm, the import results page displays the log of imported entities and their status. Imported entities can be found on the left pane, while the results of their import are presented on the right pane of the window.
  2. Click on Close to exit the import result page.



  • The import can have four results:
    • Success: all data has been imported successfully.
    • Warning: there were items during the import that could not be identified, therefore no action has been taken on those items.
    • Error: Ez folyamatbeli hiba lehet, pl hibás JSON file. Ettől még az import sikeres lehet, csak ellenőrizni kell az adott beállítást.
    • Failed: a fatal error has occurred, the import is failed, no action has been taken on any of the items.
      • New entity esetében nem jön létre új entitás (illetve létrejön, csak törlöm)
      • Felülírás esetében a cél entity-ben nem módosul semmi.
  • On the results page a link is displayed next to the entity which takes you to the edit page of the entity.
  • The import log can be found in the browser's console as well in a JSON format.

If all the above steps are carried out properly, you should now have all the configurations of the backup file in your system.


  • No labels