Unable to migrate runbooks to git unless project variables are migrated first in legacy configuration as code project

[patrick-smergut-octopus]

Severity

Possibly impacting many, confusing but minor inconvenience

Version

2025.3.61

Latest Version

None

What happened?

With legacy Configuration as Code projects where only the deployment process has been migrated to Git, a user may try to migrate runbooks to git since this is a supported feature. Projects where the project variables have been migrated will show the Migrate Runbooks to Git option, but the variables have to be migrated first for this option to be displayed.

We have variable migration guidance here: https://octopus.com/docs/projects/version-control/converting/migrating-variables

Most likely, this is due to the order we rolled out support for features, where deployment processes were first supported, then project variables, and now runbooks. However, this can be confusing when going through projects and migrating these components to Git since this order isn't obvious.

Reproduction

1. Create a project in a pre 2022.3.10382 release (this is the version in which we released variable support)
2. Upgrade Octopus to a recent version (e.g., 2025.3.61)
3. Go to Project > Runbooks and attempt to migrate runbooks to git, and see there is no Migrate Runbooks to Git option

If you migrate project variables first and then revisit the runbooks section, the option will appear:

Error and Stacktrace

More Information

Inititally reported here [internal]: https://octopus.zendesk.com/agent/tickets/238638

Workaround

Migrate project variables to git first, then the Migrate Runbooks to Git option will appear in the runbooks section.