Channel scoping for Jira CR variable isn't respected when deploying

[calverp]

Severity

No response

Version

2026.3.1737

Latest Version

I could reproduce the problem in the latest build

What happened?

When using Jira ITSM, you can create a project variable to set the CR number to be used.
If you set this variable (Octopus.JiraServiceManagement.ChangeRequest.Number) and scope it to a specific channel, releases created in a different channel will attempt to use that variable value.
I would expect the variable value to be unavailable due to it being scoped to a different channel.

Reproduction

1. Define Octopus.JiraServiceManagement.ChangeRequest.Number as a project variable with a dummy value (e.g. ITSMID-40285)
2. Apply a Channel scope to that variable (e.g. Channel 2)
3. Enable Jira CR on the project and relevant environment
4. Create a release for a different channel to the one the variable is scoped to (e.g. Channel 1)
5. Deploy the release, check the task log and it will be attempting to use the CR from the variable

Error and Stacktrace

More Information

Workaround

No response