unable to create Test execution via api endpoint https://xray.cloud.getxray.app/api/v2/import/execut

[Santhosh Polu]

we are trying to create a Test execution using

https://xray.cloud.getxray.app/api/v2/import/execution

we are getting response as 

"Can't create Test Execution for project SAPTR because Test Execution issue type is not configured!".

i have clientid, client secret. Authentication is successfull. 

```

{
"info": {
"summary": "Execution linked",
"project": "SAPTR ",
"testPlanKey": "SAPTR -837"
},
"tests": [
{
"testKey": "SAPTR -377",
"status": "PASS"
}
]
}

```

this is the payload i am sending. Always getting the above response. i have setup all the types properly in Xray and Jira

[Germán Morales _ Hiera]

Hi @Santhosh Polu , look closely at the keys in your payload: "SAPTR " has a trailing space, and "SAPTR -837" and "SAPTR -377" have a space before the dash. Xray can't match "SAPTR " to your real project, so it falls back to reporting the Test Execution type as not configured even when it is. Send them without spaces, so "SAPTR", "SAPTR-837" and "SAPTR-377", and that error should clear.

If you clean up the spacing and it still fails, then take the message at face value: the Test Execution issue type isn't in project SAPTR's issue type scheme, or it isn't enabled for that project in Xray's settings. Add it in both places and the import/execution call will be able to create the execution.

[Santhosh Polu]

copy paste error. i have configured issue types. still i am getting this error

[Germán Morales _ Hiera]

Then the gap is on the Xray side, not Jira's. Having Test Execution in the project's issue type scheme isn't enough: Xray keeps its own Issue Type Mapping that tells it which Jira types count as Test, Test Plan, Test Execution and so on, per project. If SAPTR isn't covered there with Test Execution mapped, the import reports it as not configured even though the type exists in Jira. Check it under your Jira apps settings, Xray, Issue Type Mapping.

The other thing to confirm is the project style. If SAPTR is team-managed, Xray's mapping doesn't apply the same way and you have to run Xray's dedicated team-managed quick setup to register its issue types; company-managed projects pick up the standard mapping automatically. That mismatch produces exactly this error.