Automatically create Freshservice Change Requests from Azure DevOps release pipelines with AI-powered field population.
Features
- AI-Powered — LLM analyzes PR, work items, SonarQube, Trivy to populate risk, impact, description
- Zero Dependencies — Python stdlib only, no pip install needed on agents
- Smart Triggers — Creates CR for PR merges and redeployments, skips manual patching
- Auto Requester — Resolves Freshservice requester from PR author email
- Graceful Fallback — Falls back to cr-metadata.json defaults if LLM unavailable
Usage
Add the "Create Freshservice Change Request" task to your release pipeline and configure:
- Freshservice API Key & Base URL
- Agent, Group, Department IDs
- Path to cr-metadata.json in your build artifact
- (Optional) LLM endpoint for AI analysis
- (Optional) SonarCloud API key and Trivy report path
Output Variables
| Variable | Description |
|---|---|
CR_ID |
Freshservice Change Request ID |
CR_URL |
URL to the created CR |
CR_REQUIRED |
true or false |