BMC Helix to Azure DevOps Requests
Automated Azure DevOps work item creation from BMC Helix Digital Workplace service requests so development teams act on helpdesk submissions instantly.
When a user submits a service request in BMC Helix Digital Workplace, someone on the IT team has to read it, decide if it requires a development task and manually create a work item in Azure DevOps. This Integration Pack automates that routing decision by monitoring Helix Digital Workplace for qualifying service requests and automatically creating a linked Azure DevOps work item with the request details, description and priority. Development and IT operations teams receive structured work items from Helix without any manual translation or re-entry.
Without this integration, the path from a Helix service request to an Azure DevOps work item runs through a human triage step that is often inconsistent and slow. Service requests queue in Helix Digital Workplace without any corresponding development task until someone on the IT team reviews them, interprets the request, judges its development relevance and manually creates the work item. High volumes of requests mean this triage step falls behind, development teams receive incomplete or poorly formatted work items, and there is no reliable audit trail linking the original service request to the development task it generated.
With the integration running, qualifying service requests submitted in Helix Digital Workplace flow directly into Azure DevOps as structured work items the moment they are logged. Development teams see a consistent, correctly formatted work item with the full request context already included, without any manual interpretation by IT staff. The time between a user submitting a request and a developer receiving an actionable work item shrinks from hours to seconds, and the traceability between the service request and its corresponding development task is maintained automatically throughout the workflow.
Watch the agent run, end to end
Why deploy this use case
Every validated BMC Helix Digital Workplace service request instantly creates a matching Azure DevOps work item with title, description and priority - no manual escalation.
Required fields in the service request are checked before work item creation so incomplete or miscategorised requests never reach the development queue.
Azure DevOps work item progress syncs back to the originating Helix service request so submitters and IT managers always see the current state.
The assigned development team in Azure DevOps is notified the moment a new work item is created from a Helix service request.
Every service request and its linked Azure DevOps work item are logged in both platforms, giving IT and compliance teams a reliable record.
IT teams stop copying service request details into Azure DevOps by hand - submission, validation and work item creation happen automatically.
Questions teams ask
How quickly can we get the BMC Helix to Azure DevOps Requests Integration Pack running?
Most teams are live the same day. Connect your BMC Helix and Azure DevOps accounts, confirm the field mapping and the agent starts running against your own data. There is no infrastructure to provision and nothing to deploy.
Do we need to write any code?
No. The Integration Pack ships with the trigger, the agent logic and the actions already configured. Everything is adjusted from the IntelliPaaS dashboard, so your operations team can own it without waiting on engineering.
How often does data sync between BMC Helix and Azure DevOps?
The agent runs on every qualifying event in BMC Helix, so records reach Azure DevOps within moments rather than waiting for an overnight batch. You can also put the Integration Pack on a schedule or trigger a run by hand when that suits your process better.
What happens if a record fails to sync?
Failed runs are retried automatically, and anything still unresolved is held in a review queue with the full error trace attached, so nothing is dropped silently. Your team is alerted and can replay the record once the cause is cleared.
Can we customise the field mapping?
Yes. Every field mapped between BMC Helix and Azure DevOps is editable, and you can layer on your own conditions, filters and transformations without leaving the Integration Pack.