• Azure DevOps is a Microsoft solution. It is a management tool for DevOps projects that ensures monitoring for tasks, deadlines, problems and calendars relating to applications.

• Work items are used to monitor functionalities and specifications, code errors, bugs, etc.

• Each work item is based on a work item type and has a unique ID.

• The work item types available are based on the processes used when creating projects, e.g. agile, scrum, etc. They can be configured differently by each team.
  • The Bug work item type is used for tracking bugs.
  • The Task work item type is used for monitoring activity and tasks.

• Work items can be assigned to other work items according to a hierarchy based on parent-child relationships.

• The procedure describes all of the steps for creating Microsoft Power Automate flows. To facilitate integration, the ZIP folders shipped with this integration contain pre-configured flows. Once you have downloaded them, you should specify the parameters specific to your environment, i.e. Azure account credentials, EasyVista server address, credentials of your Service Manager platform, etc.

• Use the search field to find the connectors and actions to be created in the MS Power Automate workflow easily.

  example  Find the actions for the Azure DevOps connector

  

• When you create workflow actions in Microsoft Power Automate, you must rename them as indicated in the procedure. This is because certain items of information in the name refer to the title of the action. If you do not respect the naming convention, the workflow will not be triggered correctly.

  Import the preconfigured flow below containing all of the steps to MS Power Automate.  See the procedure for importing flows.
          Flow Create Bug and Task work items in Azure DevOps

Add fields specific to Azure DevOps and GitHub to the SD_REQUEST table

Step 1: Ask EasyVista to add fields to the database

1. Ask EasyVista to add the following two fields.

• Field called E_ADO_NUMBER, nvarchar data type, size 20. This will store the ID of the Azure DevOps work item associated with the Service Manager ticket.

• Field called E_PR_NUMBER, nvarchar data type, size 20. This will store the number of the GitHub pull request associated with the Service Manager ticket.
   

Step 2: Add fields to the Ticket forms, i.e. Incident and Request forms

      See the detailed procedure

1. Open each Ticket form, i.e. Incident and Request forms.

2. Click  in the top banner and select Edit Form.
The main form presentation will appear.

3. Select and place the two fields in the form.

4. Click Save and click Save and Close.

The form will be refreshed.
         

Step 1: Log in to Azure DevOps

1. Log in to Azure DevOps using your Azure account credentials.

2. Click the name of your organization.

3. Click Organization settings.

Step 2: Create the Bug work item type

1. Select Boards > Process in the menu pane.
The list of DevOps processes will appear.
         

2. Select the DevOps project in which you want to monitor tickets created in Service Manager.
The list of work item types defined for the project processes will appear.
         

3. Click + New work item type.

4. Specify the information on the new work item type and name it Bug.
         

5. Click Create.
The properties of the new work item type will appear.

1. Select the Bug work item type.

2. Click New field.

3. Specify the information on storing the ticket ID in the new field and name it EZV_ID.
         

4. Click Add field.
The new field will be associated with the Bug work item type in the Custom section.
         

5. Repeat the procedure to create the second field for storing the ticket URI and name it EZV_URI.

Step 2: Import the flow to Microsoft Power Automate 

1. Log in to the Microsoft Power Automate website using your account credentials.

2. Click My flows in the left pane.

A list of your MS Power Automate flows will appear.
         

3. Click Import in the menu bar and select the file you downloaded.

Step 3: Create the connections required for the flow

1. Click the Select during import link in the Import Setup column for the relevant resource.

The window for configuring the import will appear.
         

2. Create a new connection for the resource or select an existing connection.

There is an existing connection for the resource

• Select the connection.
• Click Save.
  

There is no existing connection for the resource

• Click + Create.
  
  • An MS Power Automate instance will appear in a new Web browser tab.
  • The list of existing connections will appear.
             

• Click + New connection.

• Find the connection you want using the search field and select it from the list.

A window displaying the list of permissions to be granted to Microsoft Power Platform will appear.

• Click Create to create the new connection.

• Click Accept to accept the conditions and authorize Microsoft Power Platform access.
  • You will return to the tab displaying the list of MS Power Automate flows.
  • The new connection for the resource will appear in the list.

• Close your Web browser tab.
  You will return to the tab displaying the details of the imported package.

• Click Refresh List.
  The new connection for the resource will appear in the window for configuring the import.
           

• Select the connection and click Save.
  The  icon indicates that the connection for the resource has been correctly established.
           

3. Repeat the procedure for each connection required for the flow.
 

Step 4: Import package resources

1. Click Import.

The  icon next to each package resource indicates that the flow has been correctly imported.
         

Step 5: Configure package resources

Note: You should perform this step if a message at the top of the page informs you that package resources must be configured.

1. Click Save as new flow in the message displayed at the top of the page.

         

2. Click the action indicating an invalid connection.

The list of all existing connections for the selected type of resource will appear.
         

2. Click the connection defined for the type of resource.

The properties of the action will appear. The properties displayed depend on the type of resource.

3. Specify the connection information for the action.

4. Repeat the procedure for each action indicating an invalid connection.

5. Click Save.

• The error message for the action will disappear.

Step 6:  Configure the workflow

1. Move your cursor over the name of the flow and click .

The workflow will appear.
         

2. See the procedure for configuring the imported flow.

==> The flow is triggered when a ticket is created in Service Manager.