Issue Summary

The "Set to recur" feature currently hard-codes which fields are cloned: Summary, Due Date, and Start Date. Users can't modify this selection through the simplified recurring work UI.

When a user creates a recurring work item via "Set to recur," the generated automation rule always includes the Start Date system field in the clone action. If the Start Date field is not present in the project's field screens or issue layout, the automation throws an error on every execution:
 Unknown fields set during clone, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - Start date

The clone is created, but the error noise in audit logs is confusing and can't be resolved without adding unwanted fields to screens (undesirable UX change)

Proposed Solution

Allow users to configure which fields are included in the clone action through the simplified "Set to recur" UI on the issue, for example:

• A field picker/checklist during the "Set to recur" setup flow

• Respecting the project's screen/layout configuration (only clone fields that exist on the target issue type's layout)

• Not throwing errors for system fields that aren't configured on the project's screens