We are planning to take our hosted on-premise JIRA (server) to JIRA cloud. We presently use hosted Bitbucket and Bamboo versions and we expect those to remain on premise.
For integration of on-premise to Jira in cloud Atlassian does provide a convenient mechanism called "application tunnel" (https://support.atlassian.com/organization-administration/docs/what-are-application-tunnels/) that we used successfully. Application tunnels do NOT support Bamboo as of the date of writing this post ( Jan 2023)
Our Bamboo is behind a proxy server and behind firewall and it will need jumping through hoops to integrate it using available integration methods ( https://confluence.atlassian.com/bamkb/linking-jira-cloud-with-self-hosted-bamboo-389284242.html) .
The benefit of integrating Bamboo with Jira is documented in https://confluence.atlassian.com/bamboo/viewing-bamboo-activity-in-jira-applications-399377384.html
I am willing to forego the following abilities if we can avoid JIRA Bamboo integration
- Viewing build results ( users can navigate to the Bitbucket branch and check on builds)
- Viewing deployment information ( We can directly see that from Bamboo)
My Question is - What if we leave out integration of Bamboo with JIRA ? will that affect JIRA functionality (beyond ability to view Build and deployment results )? For example the Jira bitbucket integration is very fundamental for the ability to create branches corresponding to JIRA issues and track commits ( for code tracability) - is there something akin to that that we will lose if we refrain from integrating Bamboo with Jira
PS : I will be glad if someone points me to a way as easy as application tunnels that is available for integrating hosted Bamboo with Jira in cloud ( our hosted Bamboo is behind firewalls on a private subnet and is deployed behind a reverse proxy server )
