As a user, I would like to add Xray data at the time of the issue creation

Problem statement

In Xray Cloud, users cannot add Xray-specific data (such as Test Type, Test Steps, Preconditions, or other Xray fields) at the moment of issue creation.
The current workflow requires users to:

• Test issue
  • Test Type (e.g. Manual, Cucumber, Generic, Automation)
  • Test Steps
    • Action
    • Data
    • Expected Result
  • Preconditions
  • Test Repository location (folder assignment)
  • Cucumber/Gherkin definition (for Cucumber tests)
• Test Execution issue
  • Associated Tests (linking Tests to the Test Execution)
  • Test Environments
  • Defects at execution level
  • Execution status per Test Run
  • Test Run comments and evidence

This is inconsistent with Xray Data Center, where Xray fields are available directly in the Create Issue dialog.

This limitation introduces unnecessary friction, slows down test authoring, and increases the likelihood of incomplete or incorrectly configured test artifacts.

Impact

If solved, this would:

• Reduce friction and time-to-create for Tests and other Xray issue types
• Improve data completeness and consistency at creation time
• Align Cloud and Data Center user experience
• Lower adoption barriers for teams migrating from DC to Cloud
• Improve usability for high-volume test creation workflows

Who is impacted:

• QA Engineers
• Test Managers
• Teams creating Tests at scale
• Customers migrating from Xray DC to Xray Cloud

Frequency:
Occurs every time a Test (or Xray issue type) is created.

How users solve this today

• Create the issue with minimal information
• Reopen the issue to add Test Type, Test Steps, and other Xray data
• In some cases, rely on post-creation edits or bulk updates, increasing operational overhead

There is no equivalent workaround that provides the same efficiency as the DC Create Issue experience.

Context & examples

• In Xray DC, Xray fields are available during issue creation, enabling a single-step workflow
• In Xray Cloud, the same workflow requires multiple steps, which is especially painful for:
  • Manual test design sessions
  • Test case migration from spreadsheets
  • Training and onboarding new users
• This gap is frequently highlighted by customers comparing Cloud vs DC capabilities