Issue Summary

The "Set to recur" feature in the Work Item View generates a managed automation rule that is intentionally non-editable in the full automation rule editor. However, users can bypass this restriction by navigating to the Schedule component, clicking "Add Condition," and then immediately removing it. This activates the Save button and allows full editing of the rule — including renaming, removing/adding fields from the Clone action, and modifying the schedule.

This contradicts the intended read-only design 

Steps to Reproduce

1. Open any work item in a Jira Cloud space (e.g., a Task in a company-managed space)
2. Select Automation via the lightning bolt icon
3. Select Set to recur and complete the setup
4. Navigate to Space settings → Automation
5. Open the generated "Clone on a schedule" rule → Actions → Edit flow
6. Observe the Save button is greyed out (expected read-only state)
7. In the Schedule component, click "Add Condition"
8. Immediately delete the condition you just added
9. Observe the Save button is now active

Expected Results

The Save button should remain greyed out / disabled at all times when accessing the rule via the automation rule editor, since this is a managed rule designed to be controlled only through the simplified recurring work UI on the issue itself.

Actual Results

After adding and immediately removing a condition in the Schedule component, the Save button becomes active, allowing full editing of the managed automation rule.

Workaround

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