Thanks for your interest and enthusiasm around this feature. We definitely agree that it's very useful and is something we'd like to bring to Cloud at some point, but at this time we do not have an ETA. We'll update this issue when we have more information.
So of course I get to a new team and swear this feature is awesome. And then realize that they have cloud instead of server (where I had grown used to this awesomeness) and now I make the sad face. Come on Atlassian. Ive spent my entire career watching you guys miss the target on important features on the server. And now that everyone is moving to the cloud? Another round of "we'll get to it?" Sheesh.
I've migrated away from Atlassian Cloud products. There are a lot of problems like this throughout their cloud products. Stick to server until cloud is ready for actual production use, cloud seems more like a beta to me.
+1 - Pretty interesting decision to leave out something so integral to git workflows... Definitely cramping our team's workflow. I would have thought that this would be prioritized over 'style changes'.
Also, +1 for reasons we're considering Gitlab and JetBrains tooling.
Hey Folks! Surely this feature is needed to support seamless Jira & Bitbucket git workflow model in my, and any other, team. I've just come across this issue after ages searching for the feature. I guess there are work-arounds, but they are, well, work-arounds. Seems odd that it didn't make it from the server to the cloud. Looking forward to seeing an ETA.