Copied from https://jira.atlassian.com/browse/BAM-20803?focusedCommentId=2601141&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-2601141

We've just upgraded Bamboo to 7.2.0 any testing AnyTask Yaml support:

Some feedback from testing so far:

We have a Teams notification on fail, but it's not supported as yet it seems, however the output generated is:

notifications:
  - events:
      - plan-failed
    recipients:
# Notification recipient com.moveworkforward.bamboo.microsoft-teams-notifier:recipient.microsoftteams is not supported yet
 

Which results in "Bamboo YAML import failed: Document structure is incorrect: notifications / [0] / recipients: Property is required."

So we needed to remove the notifications block - ideally the export would realize that it should comment out the whole block if it was going to cause a non-importable Yaml as it's output

Thank you d130d6ec89e7 for feedback

We're going gradually implement YAML export for existing tasks depending on their popularity and usage statistics.

This is wonderful news, thanks for the new release.

Craig, Alexey Concerning point 3, getting the Any Task (BAM-20803) working in YAML would solve this issue as well.

This is great news indeed, we will start testing this within the next week with our production data and share observations.

Thank you craig.castlemead1 for feedback.

1. Created https://jira.atlassian.com/browse/BAM-21025
2. You just mentioned that Script task exported incorrectly, and task.builder.script is plugin key of this task. To reproduce the issue can you please provide Java Specs which produces this error?
3. After discussion with designers we decided to include all information about unsupported plan/deployment elements to produced code in form of comments. Adding  symbol to menu item would generate more confusion. I'll check if we can add more information about YAML format limitations to YAML Specs Code page header.

Great to have this functionality finally available. We've been able to easily convert our more straightforward builds (that don't require anytask support) to Yaml. 

A few pieces of feedback:

1. If a Script task is used and the script contains a # (as a comment or a #!/bin/bash ) then you get the error
2. Task com.atlassian.bamboo.plugins.scripttask:task.builder.script is not supported yet

1. For plans that can’t fully be exported as Yaml, I feel the UI isn’t as explicit as it could be, and this could trap some users - showing a  next to the Export Yaml specs option instead of relying the user noticing the comment in the resulting file would save some users headaches

+1

+1

+1

+1