Integrations and connectivity

Connection test fails

Check credentials and account format first. If the connection still fails:

verify DNS resolution and routing from the TestOps host to the target system;
check reverse-proxy timeouts and size limits;
enable debug logging by setting LOGGING_LEVEL_IO_QAMETA_ALLURE_TESTOPS_INTEGRATION=debug, restart the instance, retry the operation, then check the logs for 400 Bad Request, HTTP FAILED, or java.net.UnknownHostException.

If UnknownHostException appears, the URL in the integration settings is either wrong or unreachable from the network.

A job uploads results but cannot be started from TestOps

The integration works only in one direction (CI to TestOps). Check:

the job has a Build Server selected;
Job can be used to run tests is enabled;
the CI integration for that build server is fully configured;
the job was refreshed after any pipeline-side changes.

See: Jobs

Jenkins reports it could not create a session for a closed launch

This happens when a Jenkins pipeline is deleted and recreated with the same name. The new pipeline's build numbers collide with closed-launch history in TestOps.

Fix: rename the recreated Jenkins pipeline so TestOps creates a new job identity.

Check:

secure cookies are enabled on the TestOps side;
both systems use HTTPS;
users can reach both TestOps and Jira from their browser;
there are no URL formatting issues in the integration settings (for example, an unexpected trailing slash).

See: Jira Software Cloud, Jira Data Center

Defect status does not follow Jira issue status

Linking a defect to a Jira issue is not enough for lifecycle synchronization. Status updates require a webhook between Jira and TestOps.

Check:

a webhook is created in the TestOps Jira integration settings;
the webhook is configured on the Jira side.

See: Jira Software Cloud, Jira Data Center