You may export QB configuration as xml and store in SCM, and restore it from XML as desired. All these can be automated via step.

XML is not a code... It much harder to maintain and debug.

Do you have any future plan to support such functionality?

Thanks

No such plan unfortunately due to QB's architecture of configuration centric approach (a configuration defined repositories to get code, inheritance, etc).

I wanted to chime in that my team has been doing this for a couple years now. We have configurations to export and import any configuration or tree to and from Perforce. We had to make a script to rename the .xml file to 999.xml to avoid file name collision between our servers, and it is working very nicely. We use it to:

• develop and test new configuration changes on a test server
• export them to Perforce
• import them to the production server.
  Rarely, we also migrate hotfix changes back from production to the test environment.

Yes, XML isn't as readable as we would like, but we do all the work in the QB web UI. The only time it gets annoying is when we are looking at the Swarm reviews, and we have all gotten used to the syntax by now.