Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Xray custom fields are not displaying data.

June Duan
December 7, 2025

Why is there no data in the Autotest Status field in the test plan and test execution, but there is data in the Autotest Status field in the test cases?

2 answers

Suggest an answer

Log in or Sign up to answer
0 votes
June Duan
December 8, 2025
A few months ago, users could view the Automation Status and Automation Type (custom field) dropdown data normally in the test plan and test execution. 
Now, regular users cannot view the Automation Status and Automation Type (custom field) dropdown data in the test plan and test execution, although JQL statements can retrieve the data normally. 
Currently, only administrators can view the Automation Status and Automation Type (custom field) dropdown data in the test plan and test execution.
image.pngimage.png
image.png
0 votes
Taz
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 8, 2025

In Xray, custom fields like **Autotest Status** are issue-level fields, so their values are stored per individual Test issue. Test Plans and Test Executions don’t automatically aggregate or display the field values from linked Tests unless you’ve configured that explicitly. To surface this data, you’d need to use Xray’s built-in reports, create a custom Jira filter with JQL joining linked issues, or add a scripted/automation field that pulls the Autotest Status from the associated Tests. Check under **Project Settings > Screens** to ensure the field is on the relevant screens for Test Plan and Test Execution issue types, as missing screen configurations can also cause it to appear blank.

June Duan
December 8, 2025

The dropdown items were viewable normally a few months ago, but are currently only visible to administrators, and JQL queries can retrieve data correctly. This indicates that the field data itself exists, and basic read permissions have not been lost. The problem is not due to abnormal field data or query permissions, but rather a bug in the front end caused by recent Jira/Xray updates.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events