Uploaded image for project: 'Xray for Jira Cloud'
  1. Xray for Jira Cloud
  2. XRAYCLOUD-10933

Doc Gen Test Details section shows raw ObjectId instead of status name for dataset/iteration test steps

    XporterXMLWordPrintable

Details

    • Bug
    • Status: Open
    • Medium
    • Resolution: Unresolved
    • Xray Cloud 6.16.0
    • None
    • Document Generator
    • None
      • Xray Cloud 6.16.0
      • No Xporter Cloud installed
    • UNCOVERED

    Description

      In Xray Cloud Test Execution Report generation, test steps that belong to a dataset/iteration display the raw internal status ObjectId (e.g. "680bb4cb77b5e59b8a53706f") instead of the human-readable status name in the "Test Details" section, even for custom statuses like BLOCKED and FAILED_BUT_OK.

      Pre-conditions

      • Xray Cloud project with custom Test Step statuses configured (e.g. BLOCKED, FAILED_BUT_OK)
      • A document template (custom Velocity template confirmed; reporter also indicates it is reproducible with curated templates, not limited to custom ones) rendering ${TestRuns[n].TestSteps[r].Status} in the Test Details section
      • Test with steps that use datasets (iterations) and/or called test steps

      How to reproduce

      1. Configure Xray Cloud with custom statuses (e.g. BLOCKED and FAILED_BUT_OK)
      1. Create a document template with Velocity syntax that renders TestSteps[r].Status in the "Test Details" section
      1. Execute a Test that includes test steps with associated datasets (iterations)
      1. Generate the "Test Execution Report" using the template

      Actual result/Attachments

      Some step rows render the raw internal status ObjectId instead of the status name. Example captured from a simple template (StepNumber + Status only):

      1 PASSED

      2 PASSED

      3 PASSED

      4 680bb4cb77b5e59b8a53706f

      5 680bb4cb77b5e59b8a53706f

      6 PASSED

      ...

      16 680bb4cb77b5e59b8a53706f

      20 67dd24a7bb1637497a2e0d23

      Client-provided screenshots and an example export (QXF-2205-20260702_01.docx, page 8, steps 6-7) were shared in comments (2026-07-17) illustrating the affected "Test Details" section. Note: QXF-2205/QXF-2206 are the customer's own Test Execution/Test issue keys and are not accessible from this instance.

      Expected result

      The report should render human-readable status names (e.g. "BLOCKED", "FAILED_BUT_OK") consistently across all sections of the document, including "Test Details", regardless of whether the step belongs to a dataset/iteration.

      Attachments

        Issue Links

          Activity

            People

              bernardo.cottim Bernardo Cottim
              joao.silva João Silva
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: