Hello team,

Currently, when a custom field is removed from a screen scheme, both the field and its data disappear from issues, even if those issues are closed and set to be non-editable. This can lead to the loss of crucial data points for closed issues, as users will not see the custom field when viewing these issues.

Proposed Solution:

To address this issue, consider the following approach:

• Automatic Screen Creation for Closed Issues:
  • When a screen scheme is created for any issue type, automatically generate a dedicated screen for closed issues.{}
• Duplication of Custom Fields:
  • When a custom field is mapped to a field configuration and screen configuration, create a duplicate copy in a screen scheme specifically for closed issues.{}
• Association with Issue Status:
  • Associate the closed issue screen scheme with the issue's status rather than its type. Custom fields added to this scheme should remain visible in the closed issue screen, even if removed from the main screen scheme. This ensures users can track all custom fields and their data before the issue was closed.

This approach will help maintain visibility of important data in closed issues, enhancing data integrity and user experience.