Pushing generated tests to Jira and Xray safely

Treat push as a delivery step

Generation is drafting. Push is publishing. Connect credentials, choose the project and issue type, then review the selection before anything is created remotely. If you still need the drafting step, start with the AI test case generator for Jira before you push. For exactly what reaches Xray (Test issues, steps, Test Sets, and Test Executions), see the AI test case generator for Xray.

Confirm the destination first

Validate:

• Jira site URL and project key
• Issue type mapping for tests
• Whether Xray steps, Test Set, or Test Execution linking is required

Credential hygiene

Store API tokens and Xray client secrets in the product integrations panel. Do not paste long-lived secrets into tickets or chat.

# Prefer a scoped Jira API token for the integration user
# Rotate tokens if someone leaves the team

Review before create

Deselect weak cases. Rename vague titles. Confirm expected results are testable. A five-minute edit usually costs less than cleaning up duplicate issues later.

After a successful push

Open the created issues in Jira, spot-check a couple of step lists, and attach the work to your usual Test Set or Execution flow when Xray is enabled.