Integrations Between Service Manager, DevOps Tools and Git Version Control Tools


Integrations between Service Manager, DevOps tools and Git version control tools comprise four key flows corresponding to four scenarios:

  • Create a card in a DevOps tool
  • Approve a review in a Git version control tool
  • Merge a pull request in a Git version control tool
  • Close a pull request in a Git version control tool

Integration between Service Manager and DevOps tools (via MS Power Automate)

Create a card

         DevOps - Flow create work item - EN.png

Flow trigger Actions performed by the flow
When a ticket is created in Service Manager, an MS Power Automate flow is triggered.
  • A card is created in the DevOps tool.
  • The card contains the following:
    • The number of the Service Manager ticket
    • The title of the Service Manager ticket
    • The description of the Service Manager ticket
  • The ID of the card in the DevOps tool is saved in the Service Manager ticket.

Integrations between Service Manager and Git version control tools (via MS Power Automate)

Approve a review

         Git - Flow validate review - EN.png

Flow trigger Actions performed by the flow
When a review is approved in a Git version control tool, an MS Power Automate flow is triggered.
  • The contents of the review are retrieved.
  • An action is created in the timeline of the Service Manager ticket, together with the review comment and a direct link to the pull request.
  • The pull request number is saved in the Service Manager ticket.

Merge a pull request

Flow 1

         Git - Flow merge pull request #1 - EN.png

Flow trigger Actions performed by the flow
When a pull request is merged in a Git version control tool, an MS Power Automate flow is triggered.
  • An action is created in the timeline of the Service Manager ticket, together with the merge date, comment and a direct link to the pull request.

Flow 2

         Git - Flow merge pull request #2 - EN.png

Flow trigger Actions performed by the flow
When a Service Manager ticket is closed in Service Manager but the associated pull request is not merged, an MS Power Automate flow is triggered.
  • A notification email with a direct link to the non-merged pull request is automatically sent to the user in charge. This user will be in charge of performing the required actions.
  • Note: When a pull request is merged, flow 1 is triggered and an action is created in the timeline of the ticket.

Integration between Service Manager and DevOps tools and Git version control tools (via MS Power Automate)

Close a pull request

         DevOps and Git - Flow close pull request - EN.png

Flow trigger Actions performed by the flow
When a pull request is closed in a Git version control tool, an MS Power Automate flow is triggered.
  • When the pull request is associated with a card in the DevOps tool, the status of the card will change to Closed.
  • An action is created in the timeline of the Service Manager ticket, together with the closing date, a comment and a direct link to the pull request.
Tags:

Shortcuts

Powered by XWiki © EasyVista 2022