If the Conditions Custom Field is added to the create screen for the Pre-condition issuetype, an error shows when selecting the Pre-Condition Type in the Issue Create Dialog Screen from the Backlog Screen in a Scrum project.

 

Description
When Xray's Conditions Custom Field is added to the create screen for the Pre-condition issuetype, an error shows when selecting the Pre-Condition Type in the Issue Create Dialog Screen from the Backlog Screen in a Scrum project.

This happens only when opening the Issue Create Screen dialog window from this particular screen.

This happens only if the Conditions Custom Field is added to the create screen.

Although an error shows her regarding the Conditions Custom Field,  the Pre-Condition Issue can actually be created when we close and ignore the error.

Pre-conditions

• Create/Have a Scrum project for testing in the Backlog Screen.
• Verify that the Condition Custom Field is configured to be added in the Create Issue Screen Scheme for the Pre-Condition Issue Type in this project.
   

How to reproduce

• Open the Backlog Screen.
• Select the "+ Create Issue" Button at the bottom of the Backlog Screen.
• Select the "Open in Dialog" link Button at the right of the Screen.
• With the Create Dialog open, select the Pre-Condition Issue Type.

Actual result/Attachments
When the Pre-Condition Issue Type is selected in this particular Create Dialog Screen, or the screen is open when the Pre-Condition Issue Type is selected in the Backlog Screen, an error shows up:

 

Expected result{}

There should be no error showing in this screen when selection the Pre-Condition Issue Type, as it works in the other Jira Issue Create screens.

 

Workaround

Since this is only happening on this particular Issue Create Dialog Screen, we can create the Pre-Condition Issues from the main top Jira Create Button, or the in-line Issue Create box in the Backlog Screen.

If using the Create Dialog Window in the Backlog Screen, we can close and ignore the error and still create the Pre-Condition Issue despise it.

Since the problem is related to the Condition Custom Field, if we remove this field from the Issue Create Screen scheme, the error no longer shows in the Backlog Screen.