Increase the Xray Cloud limit of 10 CI/CD configurations per Space to better support enterprise customers with large-scale Jenkins integrations and CI/CD environments.

Description
Xray Cloud currently limits the Remote Jobs Trigger feature to 10 CI/CD configurations per Space, with only 6 configurations available for selection on Test Execution/Test Plan issue types. For enterprise customers with multiple applications, environments, and Jenkins pipelines, this limit can be restrictive and may hinder adoption of Xray Cloud as part of a migration strategy.

User Friction
Enterprise customers often manage dozens of Jenkins jobs across products, teams, and release streams. The current limit of 10 configurations forces customers to consolidate or exclude required CI/CD integrations, reducing the value of the Enterprise plan's CI/CD capabilities.

Steps to Reproduce (Right Now) / Actual Result

Navigate to Space Settings → Xray Settings → Remote Jobs Trigger.
Create CI/CD configurations.
After creating 10 configurations, attempt to add an 11th configuration.

Actual Result:
The system prevents the creation of additional CI/CD configurations beyond the limit of 10 per Space.

IMPACT
Large organizations cannot onboard all required Jenkins jobs into a single Space, limiting the usefulness of automated test execution triggers and CI/CD integration workflows.

What Would Improve If Solved

• Better support for enterprise-scale CI/CD implementations.
• Easier cloud migration for customers moving from other test management solutions.
• Reduced need for workarounds and administrative overhead.
• Increased adoption of Xray Enterprise CI/CD capabilities.

Impact on Stakeholders

• QA Teams: Limited ability to trigger all required test automation pipelines.
• DevOps Teams: Need to maintain alternative triggering mechanisms outside Xray.
• Administrators: Increased configuration complexity and governance challenges.
• Business Stakeholders: Potential delays or blockers in cloud migration initiatives.

Current Workaround

• Consolidate multiple Jenkins jobs into a smaller number of umbrella pipelines.
• Distribute configurations across multiple Spaces.
• Trigger Jenkins jobs directly outside of Xray.

Context & Examples
The Xray documentation states:

"Users can create up to 10 CI/CD configurations at Space level, and from those select 6 that would be available on the Test Execution/Test Plan issue type."

Several enterprise customers maintain significantly more than 10 Jenkins pipelines that need to be triggered from Xray as part of their testing and release processes.
Concrete Example
A customer operates:

5 applications
3 environments (Dev, QA, UAT)
2 test suites per application

This results in 30 Jenkins jobs that may need to be triggered from Xray. The current limit of 10 configurations supports only one-third of the required integrations.

Workaround Risk

Increased maintenance effort.
Reduced traceability between Xray and CI/CD workflows.
Complex pipeline orchestration.
Potential customer dissatisfaction and migration delays.
Risk of customers selecting alternative test management solutions that better support enterprise-scale CI/CD integration.