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

how to move a plan with it's history to another bamboo server

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

      Ability to Export selected projects

      Originally posed in forum - http://forums.atlassian.com/thread.jspa?messageID=257247499#257247499
      "There also doesn't seem to be an option to extract a single project from Bamboo and migrate it to another"

            [BAM-18449] how to move a plan with it's history to another bamboo server

            Martyna Wojtas (Inactive) made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]

            Atlassian Update - 24 March 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 - 24 March 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) made changes -
            Labels Original: pse-request New: bamboo-bugs-grooming pse-request
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3019200 ] New: JAC Suggestion Workflow 3 [ 3603738 ]
            SET Analytics Bot made changes -
            UIS Original: 0 New: 1
            Alexey Chystoprudov made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 415979 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2703126 ] New: JAC Suggestion Workflow [ 3019200 ]

            The giant hole in the (sort of) new Bamboo "configuration as code" is that you can't export a single plan, and you can't import a single plan, at least, as far as I can tell.

            And they've built this pile of dependencies that are needed for configuration as code to work at all. Why do I need Maven on the server for this? And why are you forcing us to learn Maven? Why not just export to a file and import from a file? How do I export this during a build and check it into my source control like a reasonable, smart build system is supposed to do?

             

            Deleted Account (Inactive) added a comment - The giant hole in the (sort of) new Bamboo "configuration as code" is that you can't export a single plan, and you can't import a single plan, at least, as far as I can tell. And they've built this pile of dependencies that are needed for configuration as code to work at all. Why do I need Maven on the server for this? And why are you forcing us to learn Maven? Why not just export to a file and import from a file? How do I export this during a build and check it into my source control like a reasonable, smart build system is supposed to do?  
            Krystian Brazulewicz made changes -
            UIS New: 0
            Owen made changes -
            Backlog Order (Obsolete) Original: 4920000000
            Issue Type Original: New Feature [ 2 ] New: Suggestion [ 10000 ]

              Unassigned Unassigned
              c2b41f5c0c04 Clara Yuan
              Votes:
              4 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: