Issue Summary

When a new custom field is created and added to a workflow transition screen in a Jira Cloud company‑managed project, the field is not automatically added to the relevant field configuration on the first association. As a result, the field does not appear on the transition screen during the workflow transition. Only after removing the field from the screen and adding it again does it become visible in the field configuration and start appearing as expected.

Steps to Reproduce

1. In a Jira Cloud company‑managed project, go to:
   Project settings → Workflows and identify a workflow that has a transition which uses a dedicated transition screen.

1. Go to Jira settings → Issues → Custom fields (or Work items → Custom fields).

1. Click Create custom field, choose any supported field type (for example, a Text field), and complete the creation wizard.

• • On the “Associate screens” step, optionally do not select any screens to isolate the behaviour.

1. After the field is created, navigate to the screen configuration for the transition screen identified in step 1:

• • Via Project settings → Screens, or

• • Via Jira settings → Issues → Screens, then open the relevant screen.

1. Add the newly created custom field to this transition screen and save.

1. Go to Jira settings → Issues → Field configurations and open the field configuration used by the project and issue type where this workflow/transition applies.

1. Check whether the newly added custom field appears in this field configuration.

1. Return to the same transition screen configuration:

• • Remove the custom field from the screen.

• • Add the same custom field back to the screen and save.

1. Go back to the same field configuration from step 6 and check again for the custom field.

Expected Results

After step 5 (the first time the custom field is added to the transition screen):

• The custom field should automatically appear in the relevant field configuration for the project/issue type.

• The field should be visible and usable on the transition screen when the workflow transition is executed.

Actual Results

• After step 5:

• • The custom field does not appear in the field configuration.

• • The field is not available/visible on the transition screen when performing the workflow transition, despite being added to the screen.

• Only after step 8 (removing the field from the screen and then re‑adding it):

• • The custom field appears in the field configuration.

• • The field then becomes visible and behaves correctly on the transition screen.

This indicates that the first association between a newly created custom field and a transition screen does not correctly update the field configuration, whereas a subsequent remove‑and‑readd operation does.

Workaround

For affected admins:

1. Remove the newly created custom field from the transition screen.

1. Add the same custom field back to the same transition screen.

1. After this second association, the field appears in the field configuration and on the transition screen.