Cloning runbooks doesn't clone runbook process

[RobMcCarther]

Severity

Low

Version

Introduced in 2024.3.4172

Latest Version

I could reproduce the problem in the latest build

What happened?

When cloning a runbook, the cloned runbook appears "empty" with no runbook process, even though the source runbook has a defined process. This issue seems to be a new bug introduced in version 2024.3.6198. I have tested this in my self-hosted version of Octopus v2024.3.4762, and the runbook cloned correctly, retaining the process as expected.

Reproduction

• Navigate to project with a Runbook
• Go to 'Runbooks'
• Clone the desired Runbook(verify that it has a process)
• Notice that the cloned runbook has no process

Error and Stacktrace

No response

More Information

No response

Workaround

No response