Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,415
Community Members
 
Community Events
184
Community Groups

Automation - Ticket/Issue not transitioning on Build Deployment (w/ CircleCI)

Edited

I have an automation rule which ideally should transition an issue from `Status A` to `Status B` on a successful build deployment. 
The problem is that I can see a successful deployment, but the issue isn't transitioned. 

I'm using CircleCI w/ Jira Orb, config: 

version: 2.1

executors:
xcode_executor:
macos: xcode: 13.3.0

orbs:
jira: circleci/jira@1.3.1

jobs
:
 j
ira-automation-job:
executor: xcode_executor
steps:
- checkout
- run: bundle
- run: bundle exec fastlane jira_automation
   

workflows:
jira-automation-workflow:
jobs:
- jira-automation-job:
post-steps:
- jira/notify:
job_type: deployment

Jira Automation Rule: 
When: Build successful
Then: Transition issue to Status B

Pipeline logs: 

This job is passing, however another job in workflow is runningUpdate Jira with status: successful for 202Results from Jira: ERROR: unknown association

{
"unknownIssueKeys": [],
"unknownAssociations": [
{
"values": [
""
],
"associationType": "serviceIdOrKeys"
}
],
"acceptedDeployments": [
{
"pipelineId": "xxxx",
"environmentId": "xxxx",
"deploymentSequenceNumber": 202
}
],
"rejectedDeployments": []
}

 

 


Screen Shot 2022-04-25 at 8.50.30 PM.png

(the screenshot is for the deployment for one particular ticket - ending in `-92`)

2 answers

Update: this workflow/deployment setup is working fine now. The automation rule I had setup was incorrect. 

The rule I had:

When: Build successful
Then: Transition issue to Status B

Correct rule: 

When: Deployment successful
Then: Transition issue to Status B

Edit ^^ : pipeline logs were formatted

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events