In the life of a developer there's all kinds of bugs. From the ones that fly above your keyboard on a hot, summer day, to those who fly on your computer screen after you compiled a code. None of them is a pleasant sight. And although the first could be deal with with a bug spray, the second require a bit more work, and possibly a series of tickets regarding each iteration of the code.
Tickets, I'm sure, it's not something developers love to do. But it's extremely difficult to keep track of your project's status without them. That's why being able to automatically create and update tickets in real-time could save you a lot of time and nerves.
In today's article we're going to show how to do a bi-directional synchronization with Visual Studio Team Services and Asana, which will create or update tickets in VSTS, and send any relevant information to Asana as a newly created or updated task.
Assuming you already registered for our Trial, all you have to do is hit the login button, followed by Create a Pipeline.
The way the 2-directional sync works in Cloudpipes, is that you have to have two pipes that can interact with one another. So, if you want to continuously update an existing item, you have to create it first. That's why we're going to have two pipes.
The first pipe will begin with Work Item Created in VSTS. What that does is to trigger our pipeline each time a new item is created.
Additional custom fields could be added in order to add move values to our newly created item.
Once the item is created we'll apply a regular expression for all group of items bearing the same name.
Once the regular expression is applied, Cloudpipes will create a new task in Asana.
Our newly created task has the name and description of the VSTS ticket, and is assigned to a designated team.
As you might have noticed, this pipe is linked to another VSTS work item. This serves to establish a connection between two separate pipelines.
Now, what if you want to update the already created ticket regarding a bug, that your team just found. That's where the second pipeline comes into play.
Our second pipeline will trigger each time our bug ticket in VSTS is updated.
The next step would be to tell Cloudpipes which ticket to update. In this case we'll fetch the VSTS work item we linked previously.
Once we find the right item, we'll apply a regular expression, similar to the one from the first pipeline.
Finally, Cloudpipes will go on to update the Asana task we previously created.
This is a nice way to have two pipelines collaborate with each other on a specific project. One will create new tickets, and the other will update them if certain conditions are met.
Digital transformation shouldn't be a privilege for a chosen few. With our integration platform you'll get the power of workflow automation delivered directly to you! Get our free tutorial now!