Zephyr Squad for Jira Server migration

At first make sure, that you already have ZAPI plugin installed or your zephyr version works without it.

https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Zephyr-Jira-plugin-REST-API/qaq-p/167486

Configuration file example

Create the json file with content like:

{
  "type": "zephyr",
  "debug": true,
  "requestLog": false
  "oneByOne": true,
  "allureConfig": {
    "endpoint": "https://demo.testops.cloud/",
    "token": "allure-testops-token",
    "sslTrustAll": true,
    "projectId": 81,
    "oldApiToken": true,
    "migrationTagPrefix": "zephyr",
    "folderCfPrefix": "Section",
		"issueTrackerId": 3
  },
  "zephyrConfig": {
    "endpoint": "http://localhost:2990/jira",
    "username": "admin",
    "password": "admin",
    "sslTrustAll": true,
    "projectKey": "ZM",
    "issueType": "Test",
    "issueFilter": "and component='API' or component='UI'",
    "customStoryEpic": true,
    "issueLinksType": "Test",
		"migrateLinks": true,
    "epicCustomFieldName": "customfield_10101",
    "customFields": {
      "Priority": "Severity"
    }
  }
}

Configuration parameters

Name	Mandatory	Description	Example
commonProperties	yes	see description here: Common properties
allureConfig	yes	see description here: Allure TestOps properties
zephyrConfig.endpoint	yes	Jira instance url
zephyrConfig.username	yes	Jira username
zephyrConfig.password	yes	Jira password
zephyrConfig.sslTrustAll	no	Flag if the host validation should take place. Example "true".	true
zephyrConfig.projectKey	yes	Jira project key	ZM
zephyrConfig.issueType	yes	The name of issue type in Jira system	Test
zephyrConfig.issueFilter	no	The filter for issues you want to migrate	and component='API' or component='UI'
zephyrConfig.customStoryEpic	no	Flag to create Story/Epic custom fields based on testable issues and their epics in the Jira system	false
zephyrConfig.issueLinksType	no	Type of links to identify the story	Tests
zephyrConfig.migrateLinks	no	This flag should be set to true if you need links on issues from Zephyr	false
zephyrConfig.epicCustomFieldName	no	Technical name for the epic Jira custom field	customfield_10101
zephyrConfig.customFields	no	A list of Jira fields which need to be migrated to Allure as custom fields. Structure: "jira_field_name": "TestOps_custom_field_name"	{"Priority": "Severity"}