Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-18303

As an administrator, I'd like to configure another connector and have the triggers communicate on that connector.

    • 0
    • 1
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      Incoming triggers cannot be be configured to another connector.

      Suggested Solution

      Provide option to configured triggers to come in with through another connector.

            [BAM-18303] As an administrator, I'd like to configure another connector and have the triggers communicate on that connector.

            Atlassian Update - 27 March 2025

            Hello,

            Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.

            Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.

            Please note the comments on this thread are not being monitored.

            You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.

            To learn more about our recent investments in Bamboo Data Center, please check our public roadmap.

            Kind regards,
            Bamboo Data Center

            Ishwinder Kaur added a comment - Atlassian Update - 27 March 2025 Hello, Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself. Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap. Please note the comments on this thread are not being monitored. You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here. To learn more about our recent investments in Bamboo Data Center, please check our public roadmap . Kind regards, Bamboo Data Center

            I think this feature would greatly increase Bamboo security in the case where you have a locally hosted Bamboo server working with Bitbucket in the cloud (or any remote trigger source).

             

            Currently the user interface for Bamboo and the trigger interface share the same port.  This means that you have to expose your user interface to the outside world if you have an external trigger source.  If these two interfaces were separate you could keep your user interface private and not expose your build jobs, user login etc to potential attack.

            Phil Rittenhouse added a comment - I think this feature would greatly increase Bamboo security in the case where you have a locally hosted Bamboo server working with Bitbucket in the cloud (or any remote trigger source).   Currently the user interface for Bamboo and the trigger interface share the same port.  This means that you have to expose your user interface to the outside world if you have an external trigger source.  If these two interfaces were separate you could keep your user interface private and not expose your build jobs, user login etc to potential attack.

              Unassigned Unassigned
              mduong@atlassian.com MichaelD
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: