I'm trying to figure out how to make this integration work. As of right now, the way I'm doing things is having each individual SDP Request Template trigger a flow to create a Work Item in ADO. Same way with communication from ADO to SDP. I have them separated by Folders organized my flow as:

SDP -> ADO

ADO -> SDP

SDP Request Templated created -> Create work item in ADO (with very limited fields carrying over, only title & description)

I can't seem to get other important fields such as "Status," "Priority," "Attachment File," and etc.. to carry over.

I've tried decision logics for service requests because at some point I'd like an approval process where a service request must need an approval before being created in ADO. But every time I create a Decision Logic or Filter criteria it goes into "Filtered" but then never gets updated when the request has actually been approved, so it just sits in the ether with no work item getting created in ADO. Is there a better process of making this happen? Will I have to create more flows for it to trigger an update? (Seems a little excessive to me)

Then another issue I have is that I want two-way communication between the tickets in SDP and work items in ADO to be update whenever anyone makes any changes to certain fields, but I would like to also avoid creating more flows just for each measly update.

Are there any known ways to optimize all this or resources that I can find for a ServiceDesk Plus and Azure DevOps integration? The only one I found didn't even work for me, so I have resorted to only having (1) Trigger and (1) Create work item per flow since it's the only thing that's successfully worked for me so far.

Any help or examples that actually work would be great.