Jira Deployment Status from CI/CD
When a CI/CD pipeline deploys a build, the flow updates the related Jira issues with the deployment environment and status, transitions them (e.g. to Deployed to Staging), comments with the build link, and notifies QA in Teams. Connects pipeline events to Jira issue tracking.
Provided as-is, without warranty of any kind. Review and test each pattern in a non-production environment before deploying it to live automations. See our Terms.
Overview
This flow keeps Jira issue tracking in sync with Azure DevOps CI/CD deployments. On a schedule it finds the latest successful ADO build (the deployment), looks up the Jira issues shipped in that build (matched by fixVersion), transitions each issue to the deployment status mapped for the target environment, comments on each issue with the build number and a direct link, and notifies the QA channel in Microsoft Teams that the issues are ready to test.
Why it matters: knowing which issues are in which environment is constant manual checking. Pipeline-driven updates keep Jira reflecting reality for QA and stakeholders, with a full audit trail.
Ships Off (demo).
Use Case
Dev teams split across Azure DevOps (build/release) and Jira (issue tracking) want Jira to reflect real deployment status automatically from CI/CD - no manual status updates, no stale boards.
Flow Architecture
Hourly Poll for Deployments
RecurrencePolls Azure DevOps for the latest successful deployment build (swap for an ADO webhook for real-time).
Initialize Trace & Config
Initialize variableMints a correlation id, binds ADO account/project, Jira instance/project, env-transition map, target environment, Teams ids, and resolves the transition name for the current environment.
Get Latest Completed Build
Azure DevOps - HttpRequestGET the most recent completed+succeeded build; composes the build number (used as the Jira fixVersion) and the build link.
Get Related Jira Issues
Jira - ListIssuesJQL search project = key AND fixVersion = buildNumber.
For Each Related Issue
Apply to each (concurrency 1)Lists the issue transitions, filters to the mapped target, transitions the issue when available (UpdateTransition), and comments the environment/build number/link (AddComment_V2).
Notify QA in Teams
Teams - PostMessageToConversationPosts an HTML summary (environment, build link, count, per-issue list) to the QA channel.
Environment Variables
| Schema name | Type | Default | Description |
|---|---|---|---|
| flowlibs_ADOAccount | String | your-org | Azure DevOps organization (account) name for the ADO connector. |
| flowlibs_AdoProject | String | FlowLibs | Azure DevOps project owning the CI/CD pipelines. |
| flowlibs_JiraInstance | String | REPLACE_WITH_JIRA_INSTANCE | Jira cloud instance id - X-Request-Jirainstance header. |
| flowlibs_DeployProjectKey | String | FLOW | Jira project key whose issues are linked to the deployment. |
| flowlibs_EnvTransitionMap | String | {"Staging":"Deploy to Staging","Production":"Deploy to Production"} | JSON map of environment label to Jira transition name. |
| flowlibs_DeployEnvironment | String | Staging | Current target environment label (a key in the map). |
| flowlibs_TeamsGroupId | String | <your-team-id> | Teams Group (Team) ID of the QA channel. |
| flowlibs_TeamsChannelId | String | <your-channel-id> | Teams Channel ID of the QA channel. |
Connectors & Connections
| Connector | API name | Actions used |
|---|---|---|
| Azure DevOps | shared_visualstudioteamservices | HttpRequest |
| Jira | shared_jira | ListIssues ListTransitions UpdateTransition AddComment_V2 |
| Microsoft Teams | shared_teams | PostMessageToConversation |
Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.
Customization Guide
Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.
- Issue resolution join
- Links a build to Jira issues by fixVersion = build number. Change Compose Deployment JQL to use a deployment label, release field, or keys parsed from commit messages.
- Multi-environment
- Add Staging/Production keys to flowlibs_EnvTransitionMap and point flowlibs_DeployEnvironment at the target; clone per environment for true promotion.
- Real-time
- Replace the hourly Recurrence with an Azure DevOps release/deployment webhook trigger.
- Rollback
- Add a second transition map and a branch that reverts issue status on a failed deploy.
- Customer comms
- Add an Outlook step to notify stakeholders on Production releases.
Key Expressions
The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.
EXPR.01Latest build
The most recent completed+succeeded build.
EXPR.02Transition name for env
Resolves the Jira transition for the current environment.
EXPR.03Deployment JQL
Finds the issues shipped in the build.
EXPR.04Matching transition id
The transition id to apply.
Comments
Sign in to join the conversation.
Sign inNo comments yet. Be the first to share your experience with this flow.