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

"Unknown" reason column for customised builds when using import zip

      Summary

      Bamboo loses "reason" column/field data of a custom build when the data is imported into a bamboo instance using import/export feature.

      Steps to Reproduce

      1. Create a Bamboo build plan with a repository
      2. Run a customized build with a custom revision.
      3. Use the export feature to export the bamboo data.
      4. Use this export to import in a new (or same) Bamboo instance.

      Expected Results

      • Reason field/column should have the data listed against it.

      Actual Results

      • The reason field shows "unknown" as a reason.

      Workaround

      No workaround except not using export/import feature and going with a manual way using the native tools.

            [BAM-20106] "Unknown" reason column for customised builds when using import zip

            Martyna Wojtas (Inactive) made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            Martyna Wojtas (Inactive) made changes -
            Labels Original: onboarding New: bamboo-bugs-grooming onboarding
            Pawel Skierczynski made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 2825970 ] New: JAC Bug Workflow v3 [ 3384787 ]
            Status Original: Open [ 1 ] New: Needs Triage [ 10030 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            SET Analytics Bot made changes -
            Support reference count New: 1
            Krystian Brazulewicz made changes -
            Labels New: onboarding
            Krystian Brazulewicz made changes -
            Component/s New: Import / Export [ 12155 ]
            Occurrence Factor New: 10% [ 12830 ]
            Status Original: Needs Triage [ 10030 ] New: Open [ 1 ]
            Robhit Saxena (Inactive) made changes -
            Affects Version/s New: 6.6.2 [ 80990 ]
            Affects Version/s New: 6.3.2 [ 77327 ]
            Robhit Saxena (Inactive) made changes -
            Description Original: h3. Summary
            Bamboo loses "reason" column/field data of a custom build when the data is imported into a bamboo instance using import/export feature.


            h3. Steps to Reproduce
            # Create a Bamboo build plan with a repository
            # Run a customized build with a custom revision.
            # Use the export feature to export the bamboo data.
            # Use this export to import in a new (or same) Bamboo instance.

            h3. Expected Results
            * Reason field/column should have the data listed against it.

            h3. Actual Results
            * The reason field shows "unknown" as a reason.

            h3.Workaround
            No workaround except not using export/import feature and going with manual way using the native tools.
            New: h3. Summary
            Bamboo loses "reason" column/field data of a custom build when the data is imported into a bamboo instance using import/export feature.


            h3. Steps to Reproduce
            # Create a Bamboo build plan with a repository
            # Run a customized build with a custom revision.
            # Use the export feature to export the bamboo data.
            # Use this export to import in a new (or same) Bamboo instance.

            h3. Expected Results
            * Reason field/column should have the data listed against it.

            h3. Actual Results
            * The reason field shows "unknown" as a reason.

            h3.Workaround
            No workaround except not using export/import feature and going with a manual way using the native tools.

              Unassigned Unassigned
              rsaxena@atlassian.com Robhit Saxena (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: