Jira Connect integration fails for branches with slashes
In the logs we see:
{
"errorMessages": [
{
"errorTraceId": "xxxxxxxxxxxxxxx",
"message": "ID feature/XXX-123 is not valid, may only contain alphanumeric characters or '~.-_'"
}
]
}
This is because we use the branch name as the branch ID that we send to Jira. Since we already send the branch name and this is not used for display, we should just change this to something like a hash of the branch name.