Data Export table schemas

With the Data Export API, you can download parquet files that contain tables with raw data for different areas of your testing process.

After you set up a database, you can translate the raw data from these tables into custom dashboards and queries, or you can use an external BI tool to analyze and aggregate your tests.

This topic explains the contents of all 42 tables in the parquet files.

Projects

The projects table contains the data for a Project in your qTest instance. You can use this table to group and aggregate metrics.

Column name	Column description	Code descriptions	Foreign keys	Data type
id	Unique ID of the project. This is the table’s primary key.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
name	Project name.			varchar (100)
startdatebk	Text representation of the project’s start date.			varchar (100)
enddatebk	Text representation of the project’s end date.			varchar (100)
startdate	Unix time stamp for the project’s start.			bigint (64)
enddate	Unix time stamp for the project’s end.			bigint (64)
description	The project’s description.			text
projectstatusid	Project’s status.	101 = Active	lookup.id	boolean
issampleproject	Specifies whether or not the project is a sample.			boolean
ispatchedincidents	This field is not relevant for reporting.			boolean
automation	Specifies if Automation Integration is turned on in Automation Settings.			boolean
clonestatus	This field is not relevant for reporting.			smallint (16)
patchincidentstatus	This field is not relevant for reporting.			bigint (64)
trxid	This field is not relevant for reporting.			bigint (64)
oldid	This field is not relevant for reporting.			bigint (64)
defectworkflow	Specifies if Defect Workflow is turned on in Defect Workflow Settings. This only applies to projects that don’t use external defect integration.			boolean
customfieldtemplateid	ID of the custom field template attached to the project.			bigint (64)
internally	Specifies if the project is internal, or not accessible to the user. You can disregard internal projects in your reports.			boolean
sourceprojectid	Specifies the original project this project was cloned from, if applicable.		projects.id	bigint (64)
indexingstatus	This field is not relevant for reporting.			boolean
uuid	This field is not relevant for reporting.			varchar (255)
autopopulatecloseddate	This field is not relevant for reporting.			boolean
enforcerequiredtestexecutionfields	Specifies if Enforce required test run fields for manual tests is turned on in Test Execution Settings for a project.			boolean
createddate	Unix time stamp that indicates when the project was created.			bigint (64)
lastmoddifieddate	Unix time stamp that indicates when the project was last modified.			bigint (64)
creatorid	User who created the project.		client_users.userid	bigint (64)
lastmodifieduserid	Last user who modified the defect.		client_users.userid	bigint (64)

Defects

The defects table contains external and internal Defects in qTest. You can use this data as a key performance indicator. For example, you can check when defects were opened or closed, or you can see what projects a defect is linked to.

Column name	Column description	Code descriptions	Foreign keys	Data type
id	Unique ID of the defect. This is the table’s primary key.			bigint (64)
pid	Number of the defect ID inside the project. For example, DF-1 or DF-2.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	Project the defect is created in.		projects.id	bigint (64)
assigneduserid	User who is assigned the defect.		client_users.userid	bigint(64)
createduserid	User who created the defect.		client_users.userid	bigint (64)
summary	Defect summary.			varchar (512)
description	Defect description.			text
createddatebk	Text representation of the defect’s creation date.			varchar (100)
createddate	Unix time stamp of the defect’s creation date.			bigint (64)
targetdate	Unix time stamp of defect’s targeted resolution date.			bigint (64)
closeddate	Unix time stamp of the date the defect was closed.			bigint (64)
lastmodifieddate	Unix time stamp of the last date the defect was modified.			bigint (64)
targetdatebk	Text representation of the defect’s targeted resolution date.			timestamp
closeddatebk	Text representation of the date the defect was closed.			timestamp
projectmoduleid	Module ID of the defect’s parent project.		project_modules.id	bigint (64)
statusid	The defect’s status.	10001 = New 10005 = Closed	lookup.id	bigint (64)
typeid	The defect’s type.	10401 = Bug	lookup.id	bigint (64)
reasonid	ID number of the reason to close or defer the defect.		lookup.id	bigint (64)
priorityid	The defect’s assigned priority.	10201 = Undecided 10205 = Urgent	lookup.id	bigint (64)
severityid	The defect’s assigned severity.	10301 = Cosmetic 10305 = Fatal	lookup.id	bigint (64)
categoryid	The defect’s category, such as requirement or design.		lookup.id	bigint (64)
rootcauseid	Defect root cause.		lookup.id	bigint (64)
affectedbuildid	Build affected by the defect.		builds.id	bigint (64)
affectedreleaseid	Release affected by the defect.		releases.id	bigint (64)
targetbuildid	Target fix build for defect.		builds.id	bigint (64)
targetreleaseid	Target fix release for defect.		releases.id	bigint (64)
fixedbuildid	Build where the defect was fixed.		builds.id	bigint (64)
fixedreleaseid	Release where the defect was fixed.		releases.id	bigint (64)
osid	This field is not relevant for reporting.			bigint (64)
browserid	This field is not relevant for reporting.			bigint (64)
serverid	This field is not relevant for reporting.			bigint (64)
envotherid	This field is not relevant for reporting.			bigint (64)
previousstatusid	Previous status of defect.		lookup.id	bigint (64)
draft	Indicates if the defect is a draft. Remove any defects with TRUE values before adding defects to your reports, so you don’t include unfinished defects.	TRUE = draft		boolean
lastmodifieddatebk	Text representation of the last date the defect was modified.			varchar (100)
lastmodifieduserid	Last user who modified the defect.		client_users.userid	bigint (64)
sourcedefectid	This field is not relevant for reporting.		defects.id	bigint (64)
modifieddate	Time stamp of the last date the defect was modified.			varchar (100)
indexmodifieddate	This field is not relevant for reporting.			varchar (100)
environmentid	Environment where the defect was opened.		test_beds.id	bigint (64)
indexflag	This field is not relevant for reporting.			boolean
trxid	This field is not relevant for reporting.			bigint (64)
oldid	This field is not relevant for reporting.			bigint (64)
externalissueid	ID of an issue from a connected external project management system. For example, Jira, Ralley, or VersionOne.			varchar (50)
connectionid	ID for a defect in a connected external project management system. For example, Jira, Rally, or VersionOne.		defect_tracking_connection.id	bigint (64)
externalprojectid	External project ID from your linked project management system. For example, Jira, Rally, or VersionOne.			varchar (100)
externalissuesummary	Issue summary for defects from your linked project management system. For example, Jira, Rally, or VersionOne.			varchar (2000)
externalissuestatus	Issue status for defects from your linked project management system. For example, Jira, Rally, or VersionOne.			varchar (500)
url	This field is not relevant for reporting.			varchar (100)
externalissuetype	Issue type for defects from your linked project management system. For example, Jira, Rally, or VersionOne.			varchar (50)
externalissueuniqueid	Unique issue ID of defects from your linked project management system. For example, Jira, Rally, or VersionOne.			varchar (255)
unlinkeddefect	Indicates whether the defect is linked to a test run.			boolean

Builds

The builds table contains the data for a Build in your qTest instance.

You can use this table to illustrate the requirements in a project’s build over time. Builds are optional and not all releases might have them.

Column name	Column description	Code descriptions	Foreign keys	Data type
id	Unique ID of the Build. This is the table’s primary key. It works as an optional child of a release object, where requirements are linked to releases.			bigint (64)
pid	Number of the build ID inside the project. For example, BL-1 or BL-2.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	Project that contains the build.		projects.id	bigint (64)
releaseid	Release the build is linked to. Builds are always linked to a release.		releases.id	bigint (64)
buildname	Build name.			varchar (500)
datebk	Text representation of the build date.			varchar (100)
date	Unix time stamp of the build date.			bigint (64)
note	Contents of the Note field in the build.			text
buildstatusid	The build’s status. For example, Planned or In Progress.		lookup.id	bigint (64)
deleted	Specifies whether or not the build is deleted from qTest. Deleted builds are not visible from the qTest interface.	If the object is deleted, this is TRUE.		boolean
objorder	Order of the build in its associated release in the qTest interface, in comparison to any other builds attached to the same release.			bigint (64)
createddate	Unix time stamp of the build creation date.			bigint (64)
creatorid	User who created the build.		client_users.userid	bigint (64)
lastmodifieddate	Unix time stamp of the last date the build was modified.			bigint (64)
lastmodifieduserid	Last user who modified the build.		client_users.userid	bigint (64)
trxid	This field is not relevant for reporting.			bigint (64)
oldid	This field is not relevant for reporting.			bigint (64)

Releases

The releases table contains the data for a Release in your qTest instance.

You can use this table to aggregate completed work within a project. Releases are optional and not all projects might have them.

Column name	Column description	Code descriptions	Foreign keys	Data type
id	Unique ID of the release. This is the table’s primary key. It works as an optional child of a project object to describe a related set of builds, tests, requirements, and defects.			bigint (64)
pid	Number of the release ID inside the project. For example, RL-1 or RL-2.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	Project that contains the release.		projects.id	bigint (64)
releasename	Release name.			varchar (500)
releasedescription	Field is NULL in Data Export.			text
startdatebk	Text representation of the release’s start date. We don’t recommend using this value in SQL queries.			varchar (100)
enddatebk	Text representation of the release’s end date. We don’t recommend using this value in SQL queries.			varchar (100)
startdate	Unix time stamp for the release’s start.			bigint (64)
enddate	Unix time stamp for the release’s end.			bigint (64)
releasestatusid	Specifies the release stfaftfufs. For example, Planned, In Progress, or Closed.		lookup.id
note	Field is NULL in Data Export.			text
deleted	Specifies whether or not the release is deleted from qTest. Deleted releases are not visible from the qTest interface.	If the object is deleted, this is TRUE.		boolean
modifieduserid	Last user who modified the release.		client_users.userid	bigint (64)
modifieddate	Date the release information was modified.			timestamp
objorder	Order of the release in the Test Design tab, in comparison to any other releases.			bigint (64)
createddate	Release creation date.			bigint (64)
creatorid	User who created the release.		client_users.userid	bigint (64)
lastmodifieddate	Unix time stamp of the last date the project was modified.			bigint (64)
lastmodifieduserid	Last user who modified the project.		client_users.userid	bigint (64)
trxid	This field is not relevant for reporting.			bigint (64)
oldid	This field is not relevant for reporting.			bigint (64)

Requirements

The requirements table contains the data for a Requirement in your qTest instance. Requirements describe what needs to happen for the software you are developing to meet its objectives.

You can use the data in this table to produce grouped or aggregated metrics.

Column name	Column description	Code descriptions	Foreign keys	Data type
id	Unique ID of the requirement. This is the table’s primary key. It describes the expected behavior of the software you’re testing.			bigint (64)
pid	Number of the requirement ID inside the project. For example, RQ-1 or RQ-2.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	Project that contains the requirement.		projects.id	bigint (64)
name	Requirement name.			varchar (500)
requirement	Requirement description.			text
projectmoduleid	Module ID of the requirement’s parent project.		project_modules.id	bigint (64)
requirementtypeid	Indicates whether the requirement is functional or non-functional.		lookup.id	bigint (64)
releaseid	Release the requirement is linked to.		releases.id	bigint (64)
buildid	Build linked to the requirement.		builds.id	bigint (64)
requirementpriorityid	Indicates the requirement’s assigned priority.		lookup.id	bigint (64)
statusid	Specifies the requirement’s status. For example, Planned or In Progress.		lookup.id	bigint (64)
deleted	Specifies whether or not the requirement is deleted from qTest. Deleted requirements are not visible from the qTest interface.	If the object is deleted, this is TRUE.		boolean
objorder	Order of the requirement in the project module.			bigint (64)
lastmodifieddatebk	Text representation of the last date the requirement was modified.			timestamp
lastmodifieddate	Unix time stamp of the last date the project was modified.			bigint (64)
createddate	Requirement creation date.			bigint (64)
lastmodifieduserid	Last user who modified the requirement.		client_users.userid	bigint (64)
createddatebk	Text representation of the requirement’s creation date. We don’t recommend using this for queries.			timestamp
creatorid	User who created the release.		client_users.userid	bigint (64)

Test cycles

The test_cycles table contains the data for a Test Cycle in your qTest instance. You can use this table to group completed work inside a project.

Column name	Column description	Code descriptions	Foreign keys	Data type
id	Unique ID of the test cycle. This is the table’s primary key. It describes the testing segment of a build or a release.			bigint (64)
pid	Number of the test cycle ID inside the project. For example, CL-1 or CL-2.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	The project that contains the test cycle.		projects.id	bigint (64)
buildid	Build the test cycle is linked to.		builds.id	bigint (64)
releaseid	Release the test cycle is linked to.		releases.id	bigint (64)
parenttestcycleid	Parent test cycle, which determines test cycle hierarchy.		test)cycles.id	bigint (64)
startdatebk	Text representation of the test cycle’s start date.			timestamp
enddatebk	Text representation of the test cycle’s end date.			timestamp
startdate	Unix time stamp for the test cycle’s start.			bigint (64)
enddate	Unix time stamp for the test cycle’s end.			bigint (64)
name	Test cycle name.			varchar (500)
description	Test cycle description.			text
testcycletype	Type of test cycle.	0 = Root 1 = Recycle 2 = Normal		smallint (16)
deleted	Specifies whether or not the test cycle is deleted from qTest. Deleted test cycles are not visible from the qTest interface.	If the object is deleted, this is TRUE.		boolean
objorder	Order of the test cycle in the parent test cycle.			bigint (64)
createddate	Release creation date.			bigint (64)
creatorid	User who created the release.		client_users.userid	bigint (64)
lastmodifieddate	Unix time stamp of the last date the project was modified.			bigint (64)
lastmodifieduserid	Last user who modified the project.		client_users.userid	bigint (64)
toscauniqueid	Unique ID of the object in Tosca. Only applies for Tosca integration.			bigint (64)
toscaobjecttype	Object type in Tosca. For example, TestEvent, ExecutionList, or ExecutionEntryFolder. Only applies for Tosca integration.			varchar (128)
toscanodepath	Object node path in Tosca, or the unique ID. Only applies for Tosca integration.			text
toscaurl	Unique ID of the parent of the object in Tosca. Only applies for Tosca integration.			varchar (40)
toscarooteventid	Type of a deleted object in Tosca. For example, ExecutionList. Only applies for Tosca integration.			varchar (128)

Test suites

The test_suites table contains the data for a Test Suite in your qTest instance. You can use this table to group tests in order to represent a scope of requirements.

Column name	Column description	Code descriptions	Foreign keys	Data type
id	Unique ID of the test cycle. This is the table’s primary key. It contains test cases assigned to a test cycle.			bigint (64)
pid	Number of the test suite ID inside the project. For example, TS-1 or TS-2.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	Project that contains the test suite.		projects.id	bigint (64)
testcycleid	Parent test cycle that contains the test suite.		test_cycles.id	bigint (64)
testdatasetid	Indicates the specific data set for test runs in the test suite. The applicable values are in the Test Data Source system field.			bigint (64)
projecttesttypeid	Execution type assigned to the test suite. For example, Functional, Automated, Smoke, or Regression.		lookup.id	bigint (64)
releaseid	Release the requirement is linked to.		releases.id	bigint (64)
buildid	Requirement the build is linked to.		builds.id	bigint (64)
userid	User who created the test suite.		client_users.userid	bigint (64)
name	Test suite name.			varchar (500)
description	Test suite’s description.			text
plannedstartdatebk	Text representation of the test suite’s planned start date.			timestamp
plannedenddatebk	Text representation of the test suite’s planned end date.			timestamp
plannedstartdate	Unix time stamp for the test suite’s planned start.			bigint (64)
plannedenddate	Unix time stamp for the test suite’s planned end.			bigint (64)
deleted	Specifies whether or not the test suite is deleted from qTest. Deleted test suites are not visible from the qTest interface.	If the object is deleted, this is TRUE.		boolean
testbedid	Value from the Environment system field in the test suite.		test_beds.id	bigint (64)
modifieduserid	User who modified the test suite		client_users.userid	bigint (64)
modifieddate	Unix time stamp of the date the test suite was modified.			timestamp
objorder	Order of the objects in the parent object.			bigint (64)
createddate	Test suite creation date.			bigint (64)
creatorid	User who created the test suite.		client_users.userid	bigint (64)
lastmodifieddate	Unix time stamp of the date the project was modified.			bigint (64)
lastmodifieduserid	Last user who modified the test suite.		client_users.userid	bigint (64)

Test cases

The test_cases table contains the data for a Test Case in your qTest instance.

You can use this table to group test steps.

Column name	Column description	Code descriptions	Foreign key	Data type
id	Unique ID of the test case. This is the table’s primary key. It contains a specific set of test steps.			bigint (64)
pid	Number of the test case ID inside the project. For example, TC-1 or TC-2.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	The project that contains the test case.		projects.id	bigint (64)
projectmoduleid	Unique ID of the test case’s parent module.		project_modules.id	bigint (64)
name	Test case name.			bigint (64)
testcasetypeid	Test case type. For example, Manual, Automation, or Performance.		lookup.id	bigint (64)
deleted	Specifies whether or not the test case is deleted from qTest. Deleted test cases are not visible from the qTest interface.	If the object is deleted, this is TRUE.		bigint (64)
latesttestcaseversionid	Latest version of this test case.			bigint (64)
objorder	Order of the test case in the parent module.			bigint (64)
lastmodifieddatebk	Text representation of the last date the test case was modified			varchar (500)
lastmodifieddate	Unix time stamp of the last date the test case was modified.			bigint (64)
createddate	Unix times stamp of the date the test case was created.			timestamp (without time zone)
lastmodifieduserid	Last user who modified the project.		client_users.userid	bigint (64)
creatorid	User who created the release.		client_users.userid	bigint (64)
automationid	Indicates if the test case is automated using the Automation field in the test case.			bigint (64)
priorityid	The test case’s assigned priority.		lookup.id	bigint (64)
latestrunresultid	Latest test run for the test case.			bigint (64)
veraapprovalstatusid	External Vera approval status.			bigint (64)

Test case run

The test_case_run table contains the data for an uncompleted Test Run in your qTest instance.

You can use this table to view data of any test runs that you haven’t executed against a specific environment yet.

Column name	Column description	Code descriptions	Foreign keys	Data type
id	Unique ID of the test run. This is the table’s primary key. It describes the application of a test case against a test suite, as well as the details you need to run the test.			bigint (64)
pid	Number of the test run ID inside the project. For example, TR-1 or TR-2.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	Project that contains the test run.		projects.id	bigint (64)
releaseid	Release the test run is linked to.		releases.id	bigint (64)
testcycleid	If the parent of the test run is a test cycle, this contains the unique ID for the parent test cycle.		test_cycles.id	bigint (64)
testsuiteid	If the parent of the test run is a test suite, this contains the unique ID for the parent test suite.		test_suites.id	bigint (64)
testcaseid	Test case the test run is created from.		test_cases.id	bigint (64)
testversionid	Test case version the test run is linked to.		test_case_versions.id	bigint (64)
buildid	Build the test run is linked to.		builds.id	bigint (64)
userid	User who created the test run.		client_users.userid	bigint (64)
testbedid	Value selected in the test run’s Environment field.		test_beds.id	bigint (64)
projecttesttypeid	Indicates the test run’s execution type. For example, Functional, Smoke, or Automated.		lookup.id	bigint (64)
name	Test run name.			text
plannedstartdatebk	Text representation of the test run’s planned start date.			timestamp
plannedenddatebk	Text representation of the test run’s planned end date.			timestamp
plannedstartdate	Unix time stamp for the test run’s planned start.			bigint (64)
plannedenddate	Unix time stamp for the test run’s planned end.			bigint (64)
runorder	Order of the test case execution in the test suite.			bigint (64)
deleted	Specifies whether or not the test run is deleted from qTest. Deleted test runs are not visible from the qTest interface.	If the object is deleted, this is TRUE.		boolean
latesttestcaseresultid	Most recent test case result attached to the test run.		test_case_results.id	bigint (64)
lastmodifieddate	Unix time stamp of the last date the project was modified.			bigint (64)
createddate	Release creation date.			bigint (64)
lastmodifieduserid	Last user who modified the project.		client_users.userid	bigint (64)
creatorid	User who created the test run.		client_users.userid	bigint (64)
configurationid	Related configuration ID.		configurations.id	bigint (64)
priorityid	The test run’s assigned priority.		lookup.id	bigint (64)
plannedexecutiontime	Amount of time planned for test run execution. For example, in hours.			bigint (64)
latesttestexecutionresultid	Latest test run execution result.		lookup.id	bigint (64)
toscauniqueID	Unique ID of the object in Tosca. Only applies for Tosca integration.			varchar (40)
toscarooteventid	ID of the parent object in Tosca. Only applies for Tosca integration.			varchar (40)

Requirement test cases

The requirement_test_cases table contains the data for linked Requirements and Test Cases in your qTest instance.

You can use this table to identify which test cases and requirements apply to each other.

Column name	Column description	Code descriptions	Foreign keys	Data type
id	Unique ID of the test run. This is the table’s primary key. It links test cases to their applicable requirements.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
testcaseid	Linked test case.		test_cases.id	bigint (64)
requirementid	Linked requirement.		requirements.id	bigint (64)
createddate	Release creation date.			bigint (64)
lastmodifieddate	Unix time stamp of the last date the project was modified.			bigint (64)
creatorid	User who created the release.		client_users.userid	bigint (64)
lastmodifieduserid	Last user who modified the project.		client_users.userid	bigint (64)
testcaseversionid	Version of the linked test case.		test_case_versions.id	bigint (64)

Test case results

The test_case_results table contains the data for an executed Test Run in your qTest instance.

You can use this table to view test runs that you have executed in a specific environment.

Column name	Column description	Code descriptions	Foreign keys	Data type
id	Unique ID of the completed test run. This is the table’s primary key. It describes executed test runs.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
userid	User who completed the test run.		client_users.userid	bigint (64)
testcaseversionid	Version of the case associated with the test run.		test_case_versions.id	bigint (64)
testcaserunid	Version of the test run.		test_case_run.id	bigint (64)
testexecutionresultid	Test execution result.		lookup.id	bigint (64)
executiontypeid	Test type. For example, Functional or Regression.		lookup.id	bigint (64)
buildid	Build the test results are linked to.		builds.id	bigint (64)
releaseid	Release the test results are linked to.		releases.id	bigint (64)
plannedstartdate	Time stamp for the test execution’s planned start.			bigint (64)
plannedenddate	Unix time stamp for the test execution’s planned end.			bigint (64)
executionstartdate	Unix time stamp for the test execution’s actual start date.			bigint (64)
executionenddate	Unix time stamp for the test execution’s actual end date.			bigint (64)
assigneduserid	User assigned to the test run.		client_users.id	bigint (64)
customfieldvalues	JSON representation of custom fields associated with the test log. It includes any associated values.			text
plannedexecutiontime	Amount of time planned for test run execution. For example, in hours.			bigint (64)
actualexecutiontime	Actual amount of time it takes to complete the test run.			bigint (64)
automation	Indicates if the test run is automated using the Automation field in the test case.			boolean
testcaseid	Test case the completed test run is linked to.		test_cases.id	bigint (64)
deleted	Specifies whether or not the completed test run is deleted from qTest. Deleted test runs are not visible from the qTest interface.	If the object is deleted, this is TRUE.		boolean
projectid	Project the test run was completed in.		projects.id	bigint (64)

Test case results defects

The test_case_results_defects table contains the data for any executed Test Run linked to Defects in your qTest instance. You can use this table to associate defects to test case results.

Column name	Column description	Code descriptions	Foreign keys	Data type
id	Unique ID of the test defect linked to the test run. This is the table’s primary key. It describes defects related to test cases from completed test runs.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	Project that contains the defect.		projects.id	bigint (64)
resultid	Object ID of either a Test Step Log or a Test Log, as determined from the resulttype column.			bigint (64)
defectid	Defect linked to the test result.		defects.id	bigint (64)
externalissueid	ID of an issue from a connected external project management system. For example, Jira, Ralley, or VersionOne.			varchar (50)
externalissuesummary	Issue summary for defects from your linked project management system. For example, Jira, Rally, or VersionOne.			varchar (2000)
externalissuestatus	Issue status of defects from your linked project management system. For example, Jira, Rally, or VersionOne.			varchar (500)
integrationconnectionid	ID of the external project management system that hosts the defect. For example, Jira, Rally, or VersionOne.			bigint (64)
externalprojectid	Project a defect from an external project management system is located in. For example, Jira, Rally, or VersionOne.			bigint (64)
resulttype	Object type of the result.	10 = Test Log 20 = Test Step Log		bigint (64)
externalissuetype	Issue type of defects from your linked project management system. For example, Jira, Rally, or VersionOne.			varchar (50)
testcaseid	Test case the completed test run is linked to.		test_cases.id	bigint (64)
testcaserunid	Test run the defect is linked to.		test_case_run.id	bigint (64)
testcaseversionid	Version of the test case the completed test run is linked to.		test_case_versions.id	bigint (64)
deleted	Specifies whether or not the link between the test result and defect is deleted from qTest.	If the object is deleted, this is TRUE.		boolean

Lookup

The lookup table contains the premade value options for all dropdown fields in qTest, such as Severity, Priority, or Status.

Column name	Column description	Code descriptions	Foreign keys	Data type
id	The unique ID of the lookup. This is the table’s primary key. It contains the system-standard possible values and IDs referenced by many other tables.			bigint (64)
lookupvalue	Defines the different values for pregenerated system fields.			varchar (100)
lookuptypeid	Connects the lookupvalue to the qTest interface. For example, test case type, requirement priority, or defect reason.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	Project ID.		projects.id	bigint (64)
systemvalue	Indicates whether the lookupvalue is pregenerated in qTest.			boolean

Test beds

The test_beds table stores environmental variables for each project. You can use the data in this table to filter or group based on the metadata of a test case.

Column name	Column description	Code description	Foreign keys	Data type
id	Unique ID of integrated objects. This is the primary key.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	The project that contains the test bed.		projects.id	bigint (64)
name	The name of the test bed.			varchar (210)
deleted	Specifies whether the test bed is deleted from qTest.	If the object is deleted, this is TRUE.		boolean

Custom fields

The custom_fields table holds the definitions of the custom fields for all object types.

As the qTest instance admin can define custom fields and their data, how and when the data can be used varies significantly.

Column name	Column description	Code description	Foreign keys	Data type
id	Custom field ID. This is the primary key.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	The project that contains the test bed.		projects.id	bigint (64)
objecttypeid	Internal qTest types.		object_types.id	bigint (64)
datatypeid	Internal data type ID.		custom_field_data_types.id	bigint (64)
name	Custom field name.			varchar (100)
active	Specifies whether the field is active.			boolean
systemfield	Connects the custom field to the system field location.			varchar (255)
sitefieldid	The site field linked to the custom field.		custom_fields.id	bigint (64)
defecttrackingconnectionid	The connection ID to pull the custom field in, if it comes from an external source.		defect_tracking_connection.id	bigint (64)
integrationdefectfieldid	The integration defect field ID, if it’s a defect from an external system.			bigint (64)
integrationcustomfieldid	The integration custom field ID, if it’s a custom field from an external system.			bigint (64)
createddate	Creation date of the external issue.			bigint (64)
lastmodifieddate	Modification date of the issue information.			bigint (64)
creatorid	User who created the custom field.		client_users.userid	bigint (64)
lastmodifieduserid	User who last modified the custom field.		client_users.userid	bigint (64)

Custom field values

The custom_field_values table holds the values related to custom fields.

Column name	Column description	Code description	Foreign keys	Data type
id	Unique ID of custom field values. This is the primary key.			bigint (64)
customfieldid	Related custom field ID.		custom_fields.id	bigint (64)
objectid	ID of the qTest object associated with the custom field. For example, a defect or test case.			bigint (64)
value	Actual value chosen within a specific scenario instance.			text
clientid	Unique tenant ID.			bigint (64)
projectid	Project the custom values were selected for.		projects.id	bigint (64)
objecttypeid	Object type related to the custom field value.		object_types.id	bigint (64)

Custom field configurations

The custom_field_configurations table stores the available values of the custom fields.

Column name	Column description	Code description	Foreign keys	Data type
id	Unique ID of custom field configuration. This is the primary key.			bigint (64)
customfieldid	Related custom field ID.		custom_fields.id	bigint (64)
attribute	Defines the different aspects of values for a custom field. For example, defaultValue, values, or prefix.			varchar (100)
value	Custom field value parameters. For example, pattern, default, list, or prefix.			text
valueid	Refers to lookup.id, if the attribute is sourceField. Otherwise, refers to custom_fields.id.			bigint (64)
sitefieldconfigurationid	Original value definition for a field, if the value is inherited from a site field.		custom_field_configurations.id	bigint (64)
clientid	Unique tenant ID.			bigint (64)

Custom Field Data types

The custom_field_data_types table is a static table, which means the user doesn’t affect the data it contains.

Column name	Column description	Code description	Data type
id	Custom field data type ID.		bigint (64)
type	Internal name.		varchar (245)

Project modules

The project_modules table holds information about the Modules in the qTest Requirements or Design tabs. Modules act as logical sub-groupings of a project.

Column name	Column description	Code description	Foreign keys	Data type
id	Unique ID of project modules. This is the primary key.			bigint (64)
pid	Number of the module ID inside the project. For example, MD-1 or MD-2.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	Project that contains the module.		projects.id	bigint (64)
parentmoduleid	Parent module ID for the project or parent folder in storage hierarchy.		project_modules.id	bigint (64)
name	Project module name.			varchar (500)
description	Module description. This field is NULL in Data Export.			text
deleted	Specifies whether the module is deleted.	If the object is deleted, this is TRUE.		boolean
createddate	Project module creation date.			bigint (64)
creatorid	User who created the project module.		client_users.userid	bigint (64)
lastmodifieddate	Date the project module was last modified.			bigint (64)
lastmodifieduserid	User who last modified the project module.		client_users.userid	bigint (64)

Requirement link data

The requirement_link_data table stores links between Requirements and Releases or Builds.

You can use this table to aggregate by build or release scope.

Column name	Column description	Code description	Foreign keys	Data type
id	Unique ID of requirement_link_data. This is the primary key.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	Project that contains the linkage and artifacts.		projects.id	bigint (64)
releaseid	Release with the linked data.		releases.id	bigint (64)
requirementid	Requirement linked with the release or build.		requirements.id	bigint (64)
buildid	Build linked with the requirement.		builds.id	bigint (64)
createddate	Unix timestamp (date) when the requirement was added to the release or build scope.			bigint (64)
lastmodifieddate	Unix timestamp (date) when the linkage was last modified.			bigint (64)
creatorid	User who created the linkage.		client_users.userid	bigint (64)
lastmodifieduserid	Last user who modified the linkage.		client_users.userid	bigint (64)

Test step result defects

The test_step_result_defects table stores the links between test steps and defects. You can use this data to build associations between test steps and caught defects.

Column name	Column description	Code description	Foreign keys	Data type
id	Record ID.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
teststepresultid	The test step log, or test result, that’s linked to the defect		test_step_results.id	bigint (64)
defectid	The defect linked to the test step log, or test result.		defects.id	bigint (64)
externaldefectid	External ID of the defect issue in an external tracking system, such as Jira.			varchar (50)
defecttrackingconnection	Unique ID of the defect tracking connection for the external tracking system, such as Jira or Rally.			bigint (64)

Object types

The object_types table is a static table, which means the user doesn’t affect the data it contains. You can use it to determine the object type through the object assignments table.

Column name	Column description	Code description	Data type
id	Object type ID.		bigint (64)
type	Internal object type name.		varchar (255)
name	Actual object name.		varchar (100)

Object assignments

The object_assignments table contains information on user ID assignments for Test Cases, Requirements, Modules, Test Suites, and Test Runs.

You can use it to query to identify which objects are assigned to which users.

Column name	Column description	Code description	Foreign keys	Data type
id	Unique ID for object_assignments. This is the primary key.			bigint (64)
objectid	Object with the specific user assignment. The target table is determined by the objecttypeid field, such as requirements or test cases.			bigint (64)
userid	User the object, such as a test case, is assigned to.		client_users.userid	bigint (64)
targetdatebk	Text representation of the target date.			timestamp
targetdate	Unix timestamp of the target date for the assignment.			bigint (64)
completedate	Unix timestamp of the date the assignment was completed.			bigint (64)
completedatebk	Text representation of the date the assignment was completed.			timestamp
clientid	Unique tenant ID.			bigint (64)
projectid	Project that contains the object assignment		projects.id	bigint (64)
objecttypeid	Specifies what type of object the assignment is associated with the objectid field		object_types.id	bigint (64)
assignmenttype	Assignment type.	1 = requirement 2 = test case or test design 3 = test run or test execution		smallint (16)
priorityid	Priority of the object assignment, such as low, medium, or high.		lookup.id	bigint (64)

Client users

The client_users table contains all the user metadata for your tenant. You can use it to retrieve or report on any user-related metrics and data.

Column name	Column description	Code description	Foreign keys	Data type
id	Unique ID of client_users. This is the primary key.			bigint (64)
userid	Unique user ID.		client_users.userid	bigint (64)
clientid	Unique tenant ID.			bigint (64)
status	Client status.	0 = invite sent 1 = active 2 = not used 3 = deactivated		smallint (16)
failedlogincount	Static counter of failed sign in attempts since last successful sign in for the unique user on the tenant.			smallint (16)
password	SHA1 password for the user.			varchar (256)
salt	Salt parameter used for the password for additional security.			varchar (45)
encryptedpassword	Determines if the password is encrypted.			boolean
credentialnonexpired	Determines if the credentials can expire for the unique user, which requires a password reset.			boolean
activationcode	Contains the activation code sent to the user email upon invitation.			varchar (512)
createddate	Unix timestamp of when the user was invited, or created.			bigint (64)
activateddate	Unix timestamp of when the user accepted the invite link.			bigint (64)
passwordmodifieddate	Unix timestamp of when the user last modified the password.			bigint (64)
passwordexpirationdate	Unix timestamp of when the user’s password expires if the field credentialnonexpired is not set to TRUE.			bigint (64)
lastlogintime	Unix timestamp of the last time the user logged into qTest on the tenant’s site.			bigint (64)
isshowtutorialprogressbar	Determines if a user sees the tutorial progress bar.			boolean
timezoneid	Determines the user’s timezone.			smallint (16)
defaultexectool	QTEST, QWEBEXPLORER.			varchar (60)
mappedldapid	Contains the LDAP ID of the user, if the LDAP Authentication is set up and a login name is assigned to the user.			varchar (80)
authenticatorid	Contains the Active Directory details for LDAP users, such as the CN and Ous.			varchar (256)
authtype	Determines the user’s authentication type.	Null = native user LDAP = LDAP Authentication		varchar (32)
externalauthconfigid	Points to the external authentication configuration details, such as LDAP or SSO.			bigint (64)
tzcountryid	Indicates the country the user selected on their profile.			CHAR (2)
sha3password	SHA3 Password for the user.			varchar (500)
externaluserid	Unique identifier for the External Authentication, such as LDAP or SSO. This is typically a GUID.			varchar (50)
lastmodifieddate	Unix timestamp at which the user was last modified.			bigint (64)
creatorid	User that originally sent the invite to this user.		client_users.userid	bigint (64)
lastmodifieduserid	User that last modified this user’s details.		client_users.userid	bigint (64)
firstname	qTest profile first name.			varchar (100)
lastname	qTest profile last name.			varchar (100)

Configurations

The configurations table contains information on the available legacy configurations.

Column name	Column description	Code description	Data type
setid	Refers to the parent Configuration Set. A Configuration Set defines one or more configurations.		bigint (64)
name	Generated name for this specific configuration.		varchar (255)
position	Indicates the sequence of the test run configuration relative to the Configuration Set it’s applied to.		bigint (64)
active	Determines if the configuration is active and can be assigned to a test run.		boolean
clientid	Unique tenant ID.		bigint (64)

Defect tracking connection

The defect_tracking_connection table stores all connections for a qTest project integrated with an external system. Note that this table is used for all integration connections, not just defects.

You can use the information in this table to connect data across any tables referring to external data.

Column name	Column description	Code description	Foreign key	Data type
id	Unique ID of the defect_tracking_connection. This is the primary key.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	Project where the external system connection details are set up.		projects.id	bigint (64)
name	User-specified name in qTest for the external connection.			varchar (100)
serverurl	The full URL to the instance of the external system, such as Jira or Rally.			varchar (200)
username	Username configured in qTest to access the external system.			varchar (100)
encryptedpassword	Encrpyted password that is set up for the connection to the external system. Used with the provided username to access the external system API and data.			text
active	Indicates if this connection is currently active in the qTest project.			boolean
defecttrackingsystemid	External tracking system.	1 = VersionOne 2 = Fogbugz 3 = Bugzilla 6 = Rally 7 = Jira server 6, 7, 8 = Jira Cloud 10 = Jira server 4.44 5 = Jira server 4.5 (obsolete)		bigint (64)
enabled	Indicates if the Jira connection is currently enabled in the project.			boolean
requirementenabled	Indicates if Requirement Integration is enabled for a Jira connection			boolean
migrate	Indicates if qTest manager should automatically pull data when it connects with Jira.			boolean
weburl	Contains the Web URL you provided when you configure the Jira connection in the wizard. This field is only populated for Jira Server, not for Jira Cloud.			varchar (200)
releaseenabled	Indicates if Release Integration is enabled for the Jira integration.			boolean
populateunlinkdefects	Refers to the Jira Defect Integration for the checkbox Also populate Jira defects that are not linked to Manager Test Runs.			boolean
releaseautofilter	Refers to the Jira Release Integration for the checkbox Auto-filter Test Runs on Jira iframe to match Fix Version/Sprint of Jira issue.			boolean
lastsync	Unix timestamp of the last performed sync.			bigint (64)
mergeduplicatedreleases	Indicates if the checkbox Merge all Jira Fix versions with existing Releases that have the same name is selected.			boolean
isissuemigrationconnection	Indicates if Add & Migrate was used to create this connection. This typically applies to scenarios where a Jira relinkage is required, such as a Jira Server to Jira Cloud migration.			boolean
isignoredissuemigration	Indicates whether a project admin selected Ignore after using the Add & Migrate button in Integration Settings. This is usually False, since the intent is to relink the Jira details in qTest to another instance, such as Jira Server to Jira Cloud migration.			boolean

Defect tracking project

The defect_tracking_project table contains data that associates external projects, such as from Jira Cloud, to qTest projects.

This can be used in conjunction with the defect tracking connection to describe all external projects related to qTest Projects.

Column name	Column description	Code description	Foreign keys	Data type
id	Unique ID of the defect_tracking_project. This is the primary key.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	The qTest project configured for the external project.		projects.id	bigint (64)
defectprojectid	External project ID. For Jira Cloud, this is typically the Jira project key.			varchar (100)
name	The user-friendly name of the external project.			text
defecttrackingconnectionid	Links to the connection details for the specified external project.		defect_tracking_connection.id	bigint (64)
active	Specifies whether the integration for this external project mapping is currently active in qTest.			boolean

Defect tracking type

The defect_tracking_type table contains configuration data for connections.

You can use it in conjunction with the defect_tracking_connections table to produce issue type data.

Column name	Column description	Code description	Foreign key	Data type
id	Unique ID of the defect_tracking_type. This is the primary key.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	qTest project the configuration is set up for.		projects.id	bigint (64)
name	Typically represents the external type ID. See integration_type_maps.externaltypeid.			varchar (100)
label	Represents the type name associated with the field name, such as Bug or Story.			varchar (100)
defecttrackingconnectionid	The related defect_tracking_connection ID		defect_tracking_connection.id	bigint (64)
integrationprojectid	Integrated project the linked issue type belongs to.		integration_projects.id	bigint (64)
polled	Indicates if qTest Manager is actively pulling the data from the integrated system.			boolean
lastsync	Unix timestamp of when the last sync happened.			bigint (64)

Integration external defect issue data

The integration_external_defect_issue_data table stores the field names and values metadata for defects imported into qTest and connects it to the qTest defect ID.

Column name	Column description	Code description	Foreign keys	Data type
id	Unique ID of the integration_external_defect_issue_data. This is the primary key.			bigint (64)
defectid	qTest Defect linked with the external defect.		defects.id	bigint (64)
externalissuefieldid	External field ID for a given field of the issue type.			CHAR (255)
externalissuefieldvalue	The value populated in the external system for the given field. This is for a specific issue, as determined from the integrationissuerequirementmapid.integration_issue_data field.			text
clientid	Unique tenant ID.			bigint (64)
projectid	qTest project that contains the defects.		projects.id	bigint (64)
customfieldintegrationvalueid	Links the value stored in the matching qTest custom field generated for the integration.			bigint (64)

Integration issue data

The integration_issue_data table contains the field name and value metadata for the requirement types imported into qTest, and it connects them to the imported requirement maps in the integration_type_maps table.

You can use it as the basis for a report on the field names and field values for all externally imported data.

Column name	Column description	Code description	Foreign keys	Data type
id	Unique ID of the integration_issue_data. This is the primary key.			bigint (64)
externalissuefieldid	External field ID for a given field of the issue type.			varchar (200)
externalissuefieldvalue	The value populated in the external system for the given field. This is for a specific issue, as determined from the integrationissuerequirementmapid field.			text
integrationissuerequirementmapid	Links the field values of an integrated issue with a qTest requirement.		integration_issue_requirement_maps.id	bigint (64)
customfieldintegrationvalueid	Links the value stored in the matching qTest custom field generated for the integration.			bigint (64)
clientid	Unique tenant ID.			bigint (64)

Integration issue requirement maps

The integration_issue_requirement_maps table stores the imported Requirements metadata and connects them to qTest projects and integrated projects.

Column name	Column description	Code description	Foreign keys	Data type
id	Unique ID of integration_issue_requirement_maps. This is the primary key.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	qTest project that contains the qTest requirements.		projects.id	bigint (64)
requirementid	qTest Requirement linked with the external issue.		requirements.id	bigint (64)
externalissueid	ID of an issue from a connected external project management system. For example, Jira, Ralley, or VersionOne. In Jira, this is typically with the project key. For example, ABC-1234.			varchar (200)
externalissuelink	Full URL to the external issue. For Jira this typically includes the externalissueid. For example, https://jira.company.com/browse/ABC-1234.			varchar (1000)
integrationtypemapid	Links to the defined type mapping for this integration and issue type.		integration_type_maps.id	bigint (64)
externalissueuniqueid	Unique issue ID in the external system, regardless of project.			varchar (255)
integrationprojectid	Integrated project the linked issue belongs to.		integration_projects.id	bigint (64)
connectionid	Links to the connection details for the specified integration.		defect_tracking_connection.id	bigint (64)

Integration projects

The integration_projects table contains information on connected integration projects in relation to qTest projects. You can use it to access external project metadata.

You can also use this table to join the integration issue requirement maps and the rest of the external project metadata.

Column name	Column description	Code description	Foreign keys	Data type
id	Unique ID of integration_projects. This is the primary key.			bigint (64)
isactive	Indicates if the integration project is enabled.			boolean
externalprojectid	Unique ID of the project in the external system, such as Jira.			varchar (200)
externalprojectname	Name of the project in the external system, such as Jira.			text
connectionid	Links to the connection details for the specified integration.		defect_tracking_connection.id	bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	qTest project linked with the external project.		projects.id	bigint (64)

Integration requirement field maps

The integration_requirement_field_map table contains information that you can use to identify which fields are used by the requirement configuration connection.

Column name	Column description	Code description	Foreign keys	Data type
id	Unique ID of the integration_requirement_field_maps. This is the primary key.			bigint (64)
qtestfieldname	Static name of the field in qTest that is mapped with the external field, such as ID, Project, or Status.			varchar (200)
externalfieldid	The ID number of the field in the external integration system, such as Jira ID, project, issuetype, or status.			varchar (200)
active	Indicates if this mapping is currently active.			boolean
integrationtypemapid	Indicates if the field mapping is applied to a specific integrated type, such as a Bug or a Story in Jira.		integration_type_maps.id	bigint (64)
clientid	Unique tenant ID.			bigint (64)

Integration type maps

The integration_type_maps table contains information about the issue types for external integration fields. These are not directly related to the integration issue data, but are instead related to the respective configuration table data.

Column name	Column description	Code description	Foreign keys	Data type
id	Unique ID of the integration_type_maps. This is the primary key.			bigint (64)
externaltypeid	Type ID from the external integration system, such as Jira. Values differ based on system and type. For example, these can include numeric IDs or type names such as fixVersions.			varchar (200)
externaltypename	Actual name of the type in the external integration system as it relates to the externaltypeid field. For example, in Jira, the externaltypeid fixVersions relates to the Fix Versions type name.			varchar (200)
qtesttypeid	qTest integration type.	0 = Module 1 = TestCase 2 = TestSuite 3 = TestCaseRun 4 = TestCycle 5 = Requirement 6 = Root 8 = Release 9 = TestStep 12 = Project 13 = Build 14 = Comment 15 = User 16 = SystemQueryModule 17 = Defect 27 = TestCaseVersion		bigint (64)
integrationprojectid	Integrated project the type mapping is defined for.		integration_projects.id	bigint (64)
externalfilterid	External ID to the integrated system for any specific filters applied, such as JQLs in Jira.			varchar (4000)
lastsync	Unix timestamp of when the last sync occurred.			bigint (64)
polled	Indicates if the integration type mapping has been polled.			boolean
connectionid	Links to the connection details for the specified integration.		defect_tracking_connection.id	bigint (64)
clientid	Unique tenant ID.			bigint (64)
projectid	Project this integration type mapping is set up for.		projects.id	bigint (64)

Test case versions

The test_case_versions table holds historical information for each Test Case.

Column name	Column description	Code description	Foreign keys	Data type
id	Unique ID of test_case_versions. This is the primary key.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
testcaseid	Parent test case the version record belongs to.		test_cases.id	bigint (64)
testcaseversionstatusid	Test case version status.	201 = New 202 = In Progress 203 = Ready for Baseline 204 = Baselined	lookup.id	bigint (64)
baselinenumber	Iteration of the version for a test case. This starts with 1, the second version is baseline 2, and so on.			bigint (64)
description	Test case description. Note that this information is not stored on the test case itself.			text
precondition	The test case precondition. This is also referred to as step 0. Note that this information is not stored on the test case itself.			text
deleted	Indicates if the version is deleted.	If the object is deleted, this is TRUE.		boolean
modifieduserid	User that last modified this test case version.		client_users.userid	bigint (64)
modifieddate	Unix timestamp of when the test case version was last modified.			timestamp

Test step results

The test_step_results table stores the test step results when a user executes a test step in qTest.

This table contains historical data. Information contained in this table is now contained in the test_case_results_defects table.

Column name	Column description	Code description	Foreign keys	Data type
id	Unique ID of test_step_results. This is the primary key.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
testcaseresultid	Parent test log associated with this test step log. This is the parent execution object of the entire test case.		test_case_results.id	bigint (64)
teststepid	Test step this execution result applies to.		test_steps.id	bigint (64)
testexecutionresultid	Test step result status.	601 = Passed 602 = Failed 603 = Incomplete 604 = Blocked 605 = Unexecuted	lookup.id	bigint (64)
userid	User that initiated the test step execution.		client_users.userid	bigint (64)
datebk	Text representation of the date the test step execution was initiated.			timestamp
date	Unix timestamp of when the test step execution was initiated.			bigint (64)
actualresult	Text entered by the user during test execution to describe the actual test step result.			text
resultorder	Sequence number of the test step during the execution.			bigint (64)
calledtestcaseid	If the test step uses the called test case feature, which links a test case within a test step, this contains the link to the called test case.		test_cases.id	bigint (64)
calledtestcasename	Contains the name of the test case associated with calledtestcaseid field.			varchar (500)
testcaseid	The test case that this test step belongs to.		test_cases.id	bigint (64)
testcaserunid	The test run associated with this test step log, which is the execution element for a test case.		test_case_run.id	bigint (64)
testcaseversionid	The current associated version of the test case that was approved for execution.		test_case_versions.id	bigint (64)
deleted	Indicates whether the Test Log/Test Step Log have been deleted in the UI.			boolean
projectid	The project this test step is executed in.		projects.id	bigint (64)
lastexecutedtime	Unix timestamp when the test step was last executed.			bigint (64)
executedtime	Unix timestamp when the test step was executed.			bigint (64)
lasttesterid	Most recent tester of the test step.		client_users.userid	bigint (64)
testerid	Tester associated with the test step result.		client_users.userid	bigint (64)

Test steps

The test_steps table stores the Test Steps related to a Test Case.

Column name	Column description	Code description	Foreign key	Data type
id	Unique ID of the test step. This is the primary key.			bigint (64)
clientid	Unique tenant ID.			bigint (64)
testcaseversionid	Test case version the test step was created for.		test_case_versions.id	bigint (64)
description	Describes actions the user needs to perform during test execution.			text
expectedresult	Describes the results the user expects after performing the test step.			text
steporder	Step number of the test step within the test case.			bigint (64)
runtestcaseversionid	References the most recent test case version associated with the test steps		test_case_versions.id	bigint (64)
testcaseid	Test case the test step belongs to. The version linked in the testcaseversionid field always refers to this test case.		test_cases.id	bigint (64)

Date dim

The date_dim table is a static table, which means the user doesn’t affect the data it contains.

You can use it to report in various date formats.

Column name	Column description	Code description	Data type
id	Unique ID of date_dim, which is defined as (YYYY * 10,000) + (mm * 100) + dd. This is the primary key.		integer (32)
date	Date in date format.		date
dateshort	Date in varchar format.		varchar (12)
datemedium	Date in varchar MMM dd, YYYY format.		varchar (16)
datelong	Date in varchar MMMM dd, YYYY format.		varchar (24)
datefull	Date in varchar dddd, MMMM dd, YYYY format.		varchar (32)
dayinyear	Day integer in year.		smallint (16)
dayinmonth	Day integer in month.		smallint (16)
isfirstdayinmonth	Boolean flag if first day of month.		boolean
islastdayinmonth	Boolean flag if last day of month.		boolean
dayabbr	Three-letter day abbreviation.		varchar (3)
dayname	Full day spelled out.		varchar (12)
weekinyear	Week integer in year.		smallint (16)
isfirstdayinweek	Boolean flag if first day in the week.	If the day is Monday, this is TRUE.	boolean
islastdayinweek	Boolean flag if last day in the week.	If the day is Sunday, this is TRUE.	boolean
monthnumber	Month integer in year.		smallint (16)
monthabbr	Three-letter month abbreviation.		varchar (3)
monthname	Full month name spelled out.		varchar (12)
quartername	Concatenated ‘Q’ with quarter number.		varchar (2)
quarternumber	Quarter integer in year.		smallint (16)
year	Four-digit year as an int.		smallint (16)
yearweeknumber	Varchar format concatenating YYYY, ‘-‘, and week number.		varchar (7)
yearmonthnumber	Varchar format concatenating YYYY, ‘-‘, and month number.		varchar (7)
yearmonthabbr	Varchar format concatenating YYYY, ‘-‘, and three-letter month abbreviation.		varchar (8)
yearquarternumber	Varchar format concatenating YYYY, ‘-‘, and quarter number.		varchar (6)
yearquarterabbr	Varchar format concatenating YYYY, ‘-‘, and quarter name.		varchar (7)
begdaytmsp	Timestamp of the start of the day in seconds since ‘1/1/1970’.		bigint (64)
enddaytmsp	Timestamp of the end of the day in seconds since ‘1/1/1970’.		bigint (64)

Project Module Hierarchy

The project_module_hier table contains data about the hierarchy of a project module object.

Column name	Column description	Code description	Foreign keys	Data type
clientid	Unique tenant ID.			bigint (64)
projectid	Project that contains the requirements.		projects.id	bigint (64)
id	Unique id of project_modules. This is the primary key.			bigint (64)
pid	Number of the module ID inside the project. For example, MD-1 or MD-2.			bigint (64)
name	Project module name.			varchar (500)
parentid	Parent ID project module of project module object. ID to self join.			bigint (64)
level	Indicates the number of generations away from a project module without a parent ID. The project module without a parent ID is the top ancestor.			smallint (16)
path	Ancestry ID list.	In varchar format with a ‘~’ delimiter.		varchar (400)
pathids	Ancestry ID list.	In set format {} as integers with a ‘,’ delimiter.		array
pathpids	Ancestry PID list.	In set format {} as integers with a ‘,’ delimiter.		array
pathnames	Ancestry path name list.	In set format {} as strings with a ‘,’ delimiter.		array

Report Lookup Config

This is a static table, which means the user doesn’t affect its content.

The report_lookup_config table combines some of the custom field values and lookup table values for easier reporting.

Column name	Column description	Code description	Data type
customfieldname	qTest system name.		varchar (100)
lookuptypeid	System name lookup type ID.		bigint (64)
lookupfieldname	System name lookup type name.		varchar (100)
reportfieldname	Custom fields name that displays in a report.		varchar (100)

Test Cycle Hierarchy

The test_cycle_hier table stores data about the hierarchy of a Test Cycle.

Column name	Column description	Code description	Foreign keys	Data type
clientid	Unique tenant ID.			bigint (64)
projectid	Project that contains the requirements.		projects.id	bigint (64)
id	Unique ID of the test_cycles. This is the primary key.			bigint (64)
pid	Number of the test cycle ID inside the project. For example, CL-1 or CL-2.			bigint (64)
name	Name of the test cycle.			varchar (500)
parentid	Parent ID test cycle of test cycle object. Used to self join.			bigint (64)
level	Indicates the number of generations away from a test cycle without a parent ID. The test cycle without a parent ID is the top ancestor.			smallint (16)
path	Ancestry ID list.	In varchar format with a ‘~’ delimiter.		varchar (400)
pathids	Ancestry ID list.	In set format {} as integers with a ‘,’ delimiter.		array
pathpids	Ancestry PID list.	In set format {} as integers with a ‘,’ delimiter.		array
pathnames	Ancestry path name list.	In set format {} as strings with a ‘,’ delimiter.		array

Jira Report Fields

The jira_report_fields table contains information from settings you've selected in Jira Insights Settings, where you can add any custom fields from Jira that you want to include in your Insights defect and requirement reports.

Column name	Column description	Code description	Foreign keys	Data type
clientid	Unique tenant ID.			bigint
projectid	Always set to -1.		projects.id	bigint
typeid	Indicates if the custom field is related to requirement or defect reporting in Insights.	2001 = Requirements 2002 = Defects	lookup.id	bigint
entrynumber	Entry number of custom field.			bigint
fieldname	The name of the custom field from Jira.			varchar
fieldid	Field ID from Jira for requirements or defects.			varchar
columnheading	The column header for Insights reports, containing the prefix "Jira" followed by the name of the custom field from Jira.			varchar
columntype	Type of data the custom Jira field contains, such as text or number.			varchar
columnformat	This is always set to HTML for Insights reports.			varchar