Using Hubot, you can type a command in your Visual Studio Team Services team room to create a work item, queue a build, recall what you last worked on, and more. For example, create a bug by typing "hubot vso create bug Error in latest service code" or assign a work item with the command "hubot vso assign 123 to Sally". And you can add scripts to extend what your Hubot service can do.
Set up Hubot
Set up a Hubot instance and configure the Visual Studio Team Services adapter to accept messages from a team room in Visual Studio Team Services.
If you don't already have your own Hubot instance, set one up. A good way to do that is to deploy Hubot to an Azure web site.
Create an Azure web site enabled for local Git deployment.
Create your own Hubot instance locally by cloning Hubot.
Push your configured Hubot instance to your web site.
Set the necessary configuration parameters on your site, including HUBOT_ADAPTER=vsonline, and start it.
Create a service hook subscription in your Visual Studio Team Services project that sends messages from a team room to your Hubot instance.
Here are more detailed instructions for deploying a Hubot instance to an Azure web site.
Subscribe Hubot to team room messages in Visual Studio Team Services
Now that you've set up Hubot, create a service hook subscription that will forward messages in a Visual Studio Team Services team room to your Hubot instance.
Go to a team project in your Visual Studio Team Services account and open the project adminstration page.
On the service hooks tab, add a service hook.
Select the Hubot service.
Configure an event to trigger when there are messages posted in your team room.
Select the Post a message action from the drop-down and supply the full URL and user name and password of your Hubot instance.
Click Finish to save the subscription.
Now when you post commands starting with "hubot" to the selected room, Hubot will receive the command and respond back to that room.
Here are the available Visual Studio Team Services commands available to users:
vso assign <work item list> to <user name>: Assigns one more or more work item(s) to a user (comma separated ids)
vso build <build definition number>: Triggers a build
vso builds: Shows a list of build definitions
vso commits [last <number> days]: Shows a list of commits you have made in the last day (or specified number of days)
vso create pbi|bug|feature|impediment|task <title> with description <description>: Creates a work item, and optionally sets a description (repro step for some work item types)
vso forget credentials: Removes the access token issued to Hubot when you accepted the authorization request
vso help <search text>: Get help from VS related forums about the <search text>
vso me: Shows info about your Visual Studio Team Services profile
vso projects: Shows a list of projects
vso room default <key> = <value>: Sets a room default project, etc.
vso room defaults: Shows room defaults (e.g. project, etc)
vso status: Shows status for the Visual Studio Team Services service
vso today: Shows work items you have touched and code commits you have made today
Visual Studio Team Services doesn't charge for the framework for integrating with external services. Check out the specific service's site for pricing related to their services.