PFA for the files referred in below document

ServiceDeskPlus  --> Azure DevOps

1. Create a new work-item in Azure DevOps when a request is created in SDP (using Custom Trigger + Python script)
   

Create  a Custom Trigger to execute a python script on request creation, to create a work item in Azure DevOps .

(Move create_work_item.py file to sdp_home/integration/custom_scripts folder)

• Now for the script to run, we need to configure and set the access_token
  

• To fetch an access_token, first we need to register an App in AD, follow either of the links below.
  

https://www.ecanarys.com/Blogs/ArticleID/354/Authorize-access-to-VSTS-REST-APIs-with-OAuth-2-0

https://docs.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/oauth?view=azure-devops

• After the registration, we get App ID, Client Secret and required scope as selected which will be used to fetch an authorization code
  

Now we need to authorize the registered app with the following URL

1.  https://pitstop.manageengine.com/support/manageengine/undefined &state={state} &scope={scope}&redirect_uri={callback URL}

Replace the below specified parameters with respective values,

{appID} --> client id

{state} --> Username

 {scope} -->  vso.work_full

{callback URL} - based on your configuration

Please find the example link below,

Example:

https://app.vssps.visualstudio.com/oauth2/authorize?client_id=C0FF5274-091D-4C59-96F0-CC65837CB1A9&response_type=Assertion &state=user1&scope=vso.work_full&redirect_uri=https://9c20f2fffcea.ngrok.io/

Access the above constructed endpoint URL in a browser and you would see a similar page as shown in the below image,

Click on accept and we'll be redirected to the call back url with the auth_code in the url

https://{callbackurl}/?code={authorization_code}&state=user1

Get the auth code and replace it with key in the azureDevopsSecurityConfig.json file  "auth_code" as well as Client secret Key from the registered app with the key "client_assertion"

2. Now the configuration is done, as the request is created the trigger runs the script and fetches the access_token and refresh_token using the auth_code and invokes the api to AD to create a work item.

3. For this to be done move the devopsProjectConfig.json, priority.json, azureDevopsSecurityConfig.json files to sdp_home/integration/custom_scripts folder and update the file as follows

devopsProjectConfig.json defines the project settings such as project name, username, work item type and redirect url

eg:

{"project_name":"FinTech", "user_name":"user10371", "workitem_type":"issue", "redirect_url":"https://9c20f2fffcea.ngrok.io%22%7D/

project name & username can be found in the project page of AD like below:

priority.json defines the priority mapping with SDP and AD

eg:

{"High":1,"Medium":2,"Normal":3,"Low":4}

azureDevopsSecurityConfig.json defines the auth_code and client_assertion

4. On the other part we need to create a trigger in Azure DevOps to hit the SDP REST API on status change of the work item

and for that we'll be storing a custom field in work item called 'sdp_request_id' and to add this custom field follow

https://docs.microsoft.com/en-us/azure/devops/organizations/settings/work/customize-process-field?view=azure-devops#:~:text=For%20example%2C%20you%20can%20add,form%20for%20an%20inherited%20field.&text=This%20article%20applies%20to%20Azure,Server%202019%20and%20later%20versions

5. Move AzureDevOps.jar to sdp_home/integration/lib folder

6. Move AppIntegrations_Handler_Custom.xml to sdp_home/integration/conf folder

7. Once work-item is created we are capturing the success/failure message under Request History

Once the requested is created as Work Item in AD here is how it looks

Note: Restart the SDP server.

 Azure DevOps --> ServiceDeskPlus 

 Steps: