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

Add connection information to the Environments configuration

XMLWordPrintable

    • 0

    • 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.

      Currently we have to add the connection information every time that we create a task that requires access to an environment. Instead, it would be great to configure this information once when creating the environment and allow to select the required environment from a drop down list when configuring a task.

      The information I believe would be require is.

      • Hostname
      • Password / SSH Key

            [BAM-13836] Add connection information to the Environments configuration

            Martyna Wojtas (Inactive) added a comment -
            Atlassian Update - 7 April 2020

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested.

            Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

             

            Thank you,

            Bamboo Team

            Martyna Wojtas (Inactive) added a comment - Atlassian Update - 7 April 2020 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.   Thank you, Bamboo Team

            James Dumay added a comment -

            Ahh, you are right. Sorry about that. I've re-opened this ticket.

            James Dumay added a comment - Ahh, you are right. Sorry about that. I've re-opened this ticket.

            Rodolfo Romero (Cisco) added a comment -

            To be more clear, the idea is not to allow to copy tasks or share tasks. What we want to be able to do is to have a special area where the environments are configured at a general level and then when setting up a new Deployment Project, the environments would be selected from a drop down list.

            Rodolfo Romero (Cisco) added a comment - To be more clear, the idea is not to allow to copy tasks or share tasks. What we want to be able to do is to have a special area where the environments are configured at a general level and then when setting up a new Deployment Project, the environments would be selected from a drop down list.

            Rodolfo Romero (Cisco) added a comment -

            I'm not sure this tickets is exactly described on the other ticket. This ticket specifically talks about the way "Environments" are handle in Deployment Projects. Currently, when a new "Environment" is created, the only information required is Name and Description. This should also include, "Hostname" and "Username/Password" or "Private SSH Key". Please keep this ticket opened unless you clarify the scope of the other ticket in more depth at the level this one has done it.

            Thanks,

            Rodolfo

            Rodolfo Romero (Cisco) added a comment - I'm not sure this tickets is exactly described on the other ticket. This ticket specifically talks about the way "Environments" are handle in Deployment Projects. Currently, when a new "Environment" is created, the only information required is Name and Description. This should also include, "Hostname" and "Username/Password" or "Private SSH Key". Please keep this ticket opened unless you clarify the scope of the other ticket in more depth at the level this one has done it. Thanks, Rodolfo

            James Dumay added a comment -

            This issue duplicates BAM-12426. Please watch and vote for it instead.

            James Dumay added a comment - This issue duplicates BAM-12426 . Please watch and vote for it instead.

              Unassigned Unassigned
              a5062b43438d Rodolfo Romero (Cisco)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: