Hi Team,
We are trying to set up an automation that updates the Jira issue status automatically when a GitHub Pull Request (PR) is merged.
Here’s the flow:
Each Jira issue key (e.g., BS-123
) is included in the branch name.
We suffix the environment in the branch name (e.g., BS-123-something-staging
, BS-123-hotfix-preproduction
, etc.).
When a Pull Request is created and merged, Jira recognizes the linked issue through the GitHub integration.
We want to automate status transitions based on the target branch (i.e., where the PR is merged into).
Our goal:
If a PR is merged into a branch named with staging
, the linked Jira issue should move to "QA: Not Integrated to Frontend".
If merged into pre-production
, move it to "Pre-Production: Not Integrated to Frontend".
If merged into production
, move it to "Production: Not Integrated to Frontend".
What we have implemented:
Trigger: Pull Request Merged
Condition: Smart Value Condition
Smart Value used: {{pullRequest.destinationBranch}}
Operator: Contains
Values tested: staging
, pre-production
, production
Structure: We used an if-else block structure, where each branch name condition is checked in a separate "if block" with transitions defined inside.
We also tried using {{pullRequest.destinationBranch.name}}
instead of {{pullRequest.destinationBranch}}
, but the automation still doesn't trigger the status transition correctly.
Could you please guide me on the correct smart value to use, or suggest how I should configure this?
Thanks!
Hi @naveen
Welcome to the community.
Make a variable based on the smart value, I presume you do get a result from using the smart value?
Then use a smart value condition where you compare the variable context against the required value.
Thanks @Marc - Devoteam it's working now!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @naveen
Please accept my answer as a solution, if my answer helped to solve your request.
This will help other community member trying to solve the same.
P.S. If the answer is very valuable to you, please share some kudos.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.