XRay for Jira Server migration

WARNING

MIGRATION AVAILABLE FOR ALLURE TESTOPS VERSION > 4.26.0

Configuration file example

Create the json file with content like:

{
  "type": "xray",
  "debug": true,
  "oneByOne": true,
  "allureConfig": {
    "endpoint": "https://demo.testops.cloud/",
    "token": "1f4b4acd-418c-4d0b-8533-1d747abb7599",
    "sslTrustAll": true,
    "projectId": 6,
    "migrationTagPrefix": "xray"
  },
  "xrayConfig": {
    "endpoint": "http://localhost:2990/jira",
    "username": "admin",
    "password": "admin",
    "sslTrustAll": true,
    "projectKey": "ZM",
    "issueType": "Test"
    "customFields": {
      "priority": "Priority"
    }
  }
}

Configuration parameters

Name	Mandatory	Description	Example
commonProperties	yes	see description here: Common properties
allureConfig	yes	see description here: Allure TestOps properties
xrayConfig.endpoint	yes	Jira instance url
xrayConfig.username	yes	Jira username
xrayConfig.password	yes	Jira password
xrayConfig.sslTrustAll	no	Flag if the host validation should take place. Example "true".	true
xrayConfig.projectKey	yes	Jira project key	ZM
xrayConfig.issueType	yes	The name of issue type in Jira system	Test
xrayConfig.issueFilter	no	The filter for issues you want to migrate	and component='API' or component='UI'
xrayConfig.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"}
xrayConfig.folderCfName	no	Name of custom field for folders structure	customfield_10009
xrayConfig.parametersCfName	no	Name of custom field for parameters	customfield_10028
xrayConfig.stepsCfName	no	Name of custom field for test steps	customfield_10003