The idea of having the two backlogs can still be pretty new to many people, so I will first try to explain in this posts the philosophy behind the usage of different backlogs and present the integration of different management systems. The Operations backlog or Ops backlog is usually a backlog for management of business and end users, where incidents, problems, tickets and service requests are being recorded. By monitoring and event management events are dispatched back to the Development backlog or Dev Backlog, where the main goal of the team is to deliver constant structural enhancements, to improve the satisfaction and to prevent and incidents affecting the high quality of performance and functionality for the end user.
In order to ensure a smooth connection between different backlogs, there are some good solutions on the market for incident management, such as Service Now, Remedy, Trello, ZenDesk, User Voice and much more. To get more insights from real examples, in many of my projects the development, which is using Dev Backlog was made in Visual Studio and integrated with Ops Backlogs, using different incident management apps mentioned above. The idea is well captured in the image below:
Further, in this post, I will show the example of how to make the integration between Trello and VSTS, which will enable us to see all changes in the state of work items on the boards of each application. We’ll use Zapier to connect both applications and Zapier will enable us to automate tasks between both apps.
First, we’ll need to log into Trello with a valid account.
1. For our case, we have connected with valid Google account.
2. After we log into Trello, we’ll be able to see all the teams that we can join.
3. With clicking on the team’s board Icon we’ll be able to join the team for which we want to create automation on Zapier.
4. With opening the board of the team in Trello, we see all the boards of the team. Here we can add a new board, change the colors of the current boards or any other settings of the board, such as team members for example.the colors of the current boards or any other settings of the board, such as team members for example.
5. With choosing the team’s board, a new window will appear with the board settings. On the right side of the side window, we will have the board’s settings, where we will be able to see the activity of the team, with all team members. We’ll be able also to see the Join the team button, which we need to choose in order to create an integration in later steps.
In your Zapier account, you will need to create a Zap, which is representing the integration between the apps. On the left side, you will add the triggers and on the right side, you will add the actions.
In the first Zap on the example below – Trello-… to VSTS, we can see that the trigger is set to be Trello and the action will be done in VSTS.
On the example below, you will be able to see the integration or the Zap for Trello … cards to VSTS.
1. With clicking on the arrow on the right side of the Zap.
2. You will be able to choose from the drop-down menu the Edit option, to see or edit the settings of this integration.
In this integration, we’ve set 3 steps, but please note that the step 2 is not really used and it’s unnecessary as it doesn’t provide any function. You will be able to see it, in order to just get an idea that we can use also different filters as the steps.
3. In the Connection to the Trello, where we have set different options for connection and in the first part we first chose the app for our connection, which is Trello.
4. Then we define the Trello trigger, which is in our case when the Trello card is moved to the list.
5. After that, we have defined the account with which we are connected to Trello, where is a good idea to test if the connection to the account is working fine.
6. Next, we’ll move to Edit Options, where we chose the Trello board for which we want to have the integration, the list of the stage for which we want to set the trigger and the type of the card that we want to use.
7. Once when we finish with the settings of the step, we need to test it in order to be able to move to the next settings of our integration.
8. We can set also the filters, where we set the triggers to be working only in the case where the card name doesn’t already exist so that we are able to avoid any duplication of the work items. But as explained before, this filter is not really needed for this zap as it will not do anything.
9. In the Connection to VSTS backlog, we will choose the action, which will appear in the VSTS backlog. So, first, we will connect our VSTS account.
10. Then we will choose the option, in which the new work item will be created based on the trigger from the first step.
11. We’ve chosen the account with which we are connecting to our VSTS backlog and again, before continuing to the next step of setting the integration, we need to test if the account connection if working fine.
12. We’ve edited the template, where we chose the VSTS project, the type of the Work item which will be created and the Title of the new work item, which will be in our case equal to the Trello card name. In next options, we chose the area and the description of the newly created work item, which will be the same as the Trello card description.
When we’ve set all the requirements for our integration, we need to test the settings, by going through the process.
You will see that we have created in our Zapier account three more integrations or zap’s for automation of different state changes. The same idea or philosophy was used also in this zaps, where of course we first connected both accounts and chose the appropriate steps, such as the filters which will tell us when to continue to the next step and for which state changes we want to see the automation.
For this example, we created a test card in Trello, which is not visible yet in the VSTS backlog. Considering the rules and filters that we previously set in the Zapier, when we move the card from the state Suggestions/Ideas to the Suggested Ideas – Added to TFS, we’ll see that the card will appear as a work item in our VSTS backlog.
As we set in our Zap that the trigger will run every five minutes, the work item will appear in our VSTS backlog after this five minutes. Of course, if we want to see it immediately, we can navigate to the Zapier, choose our Zap and manually set the trigger to run immediately.
We’ll see the new work item in the bottom of our backlog.
When we add our new work item in the current sprint and move it to the Committed state, we’ll be instantly able to see this change appear on the Trello board. In the image below you will see that we moved our Test Work item in the Committed state.
And we will be instantly able to see this change in our Trello board.
Remember, this will happen due to our previous settings in the Zapier, where we mapped the Committed state from VSTS backlog with the Working on the state on the Trello.
For example, if we try to move the work item in the VSTS backlog to the Groomed state, nothing will happen on the Trello board, as the Groomed state of VSTS backlog is not mapped to any state of the Trello board.
The same automation will happen when we move the work item of our VSTS backlog to the state Done, as the VSTS backlog state Done is mapped to the Deployed state of our Trello board. Again, this automation is done, based on the settings that we chose previously in our Zap.
The same automation between the work items and the Trello card can be done for any other state, such as Awaiting Deployment or Testing, we just need to set it in our Zap’s.