Skip to main content
Version: 3.0.1

Jira Test CSV Guide

Purpose and Audience​

This guide documents the structure, key fields, and usage patterns for the tests_descriptions.csv Jira export file. It is intended for QA engineers, test authors, and developers who need to look up test metadata, trace tests back to requirements, or filter the test inventory for reporting and analysis.

Overview​

The tests_descriptions.csv file contains Jira export metadata for all test cases. This is a read-only export file containing over 3,400 test records with 185 columns.

Key Fields​

These are the most commonly used fields for test organization:

Identification​

FieldDescriptionExample
SummaryTest case title"Punctuation Variation - Valid Specimen ID"
Issue keyJira issue ID"BT-5961"
Issue idNumeric ID"29823"
Issue TypeAlways "Test""Test"

Project​

FieldDescriptionExample
Project keyProject abbreviation"BT"
Project nameFull project name"Bengal Tiger"
Project typeProject category"software"

Status and Priority​

FieldDescriptionExample
StatusTest status"To Do", "In Progress", "Done"
PriorityPriority level"Low", "Medium", "High"
Status CategoryStatus grouping"To Do", "In Progress", "Done"

Description​

FieldDescriptionExample
DescriptionFull test description"Verify the system correctly identifies..."

People​

FieldDescriptionExample
ReporterWho reported"Alex"
CreatorWho created"Alex"
AssigneeWho is assigned(empty if unassigned)

Dates​

FieldDescriptionExample
CreatedCreation date"12/Dec/25 5:30 PM"
UpdatedLast update"12/Dec/25 5:31 PM"
ResolvedResolution date(empty if unresolved)

Labels​

FieldDescriptionExample
LabelsClassification labels"AI" (for AI-generated tests)

The CSV tracks relationships between issues:

FieldDescription
Inward issue link (Test)Requirements tested by this test
Outward issue link (Test)Tests linked to this requirement
Outward issue link (Defect)Bugs found by this test
Inward issue link (Cloners)Tests cloned from this test
Outward issue link (Test): BT-5894

This indicates the test is linked to requirement BT-5894.

CSV Structure​

Header Row​

Summary,Issue key,Issue id,Issue Type,Status,Project key,...

Data Row Example​

Punctuation Variation - Valid Specimen ID,BT-5961,29823,Test,To Do,BT,Bengal Tiger,software,...

Filtering Tests​

By Label​

  • AI - AI-generated tests
  • (other custom labels)

By Status​

  • To Do - Not started
  • In Progress - Being worked on
  • Done - Completed
  • Filter by Outward issue link (Test) to find all tests for a requirement

Using the CSV​

Finding Tests for a Requirement​

  1. Open in spreadsheet software
  2. Filter by Outward issue link (Test) column
  3. Enter requirement key (e.g., "BT-5894")

Finding AI-Generated Tests​

  1. Filter by Labels column
  2. Contains "AI"

Exporting a Test List​

  1. Filter as needed
  2. Select columns: Summary, Issue key, Status, Description
  3. Export filtered results

Field Mapping to Test Formats​

This table shows how CSV fields map to Cucumber feature files and manual test JSON exports.

CSV FieldCucumberManual JSONDescription
Issue key@TEST_BT-xxxxjira.keyTest identifier
SummaryScenario namejira.summaryTest title
DescriptionFeature descriptiondescriptionTest objective
Outward issue link (Test)@REQ_BT-xxxxN/ALinked requirement

For details on writing Cucumber tests, see the Testing Guide. For the manual test JSON schema, see the Manual Test Guide.

Custom Fields​

The CSV includes many Jira custom fields. Most are empty for test records:

FieldUsage
Custom field (Test Steps)Xray test steps (for Xray-native tests)
Custom field (Test plan)Associated test plan
Custom field (Epic Name)Parent epic
Custom field (Story Points)Effort estimate

Notes​

  1. Read-Only: This file is an export; edits should be made in Jira.
  2. Refresh Frequency: Re-export periodically to get updates.
  3. Column Order: May vary between exports.
  4. Empty Fields: Many custom fields are unused for test records.
  5. Date Format: Uses Jira date format (DD/Mon/YY H:MM AM/PM).