You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi
I'm trying to help a team (that have a release pipeline interacting with Jira currently) with some automation to transition the relevant story/s to Done upon completion of a successful deployment.
But we are struggling to work out what the Environment Types represent in the " Deployment Successful" trigger option.
We have data coming through showing the "environment name" (which are the Stages in their Azure DevOps Release Pipeline) but how do we trigger the automation via these "environment types" in the trigger?
Thanks @tomas but that much I knew. What I was after was how that is mapped from Azure DevOps.
The answer; via "Deployment type"
Hi @Curt Holley I am also trying configure and enable Deployments Feature in JIRA. I am using Azure DevOps release pipelines and it the release pipelines I have checked out the option "Report Deployment Status to JIRA" but unfortunately I am not receiving any deployment status back to JIRA.
Can you help me out on what worked for you while configuring Deployment feature in JIRA?
I have posted a question in the community as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How to use deployment variabale in another build plan where i am i use trigger this deployement
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So this environment is used to distinguish for which environment we want to trigger the automation rule.
So when we select `production` the rule will only trigger the rule when a commit is deployed to production.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.