Issue Summary

In Jira Cloud, when a custom field is removed from its associated screens for a given Space/Project, its values remain stored for the Work Items.

For example, Automation rules can still read these values.

Steps to Reproduce

Create a test custom field and add it to:

• A context including your test Space + Work Item type
• The Create/Edit/View screens for that Work Item type

Create a test Work Item and set a value in the custom field.

Remove the field from all screens

• Go to Screens → remove the custom field from Create/Edit/View screens for that Work Item type
• Do not delete the field or change its field context.

Create an Automation rule

• Trigger: Manual trigger or Issue transitioned.

• Action: “Log action” with
  {{issue.customfield_xxxxx}} (use your field’s ID).

 

Run the rule on the test issue

• Check the automation audit log → you will still see the custom field value, even though the field is no longer visible on the Work Item.

Expected Results

• Removing the Screen from the Work Item and its associations should clear out the value as well.

Actual Results

• The value of the custom field is retained even after the Custom field and its associations are removed.

Workaround

• Currently there is no known workaround for this behavior. A workaround will be added here when available