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

Pulkit Vaid _ Fueled April 25, 2022

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

0 votes
Pulkit Vaid _ Fueled April 26, 2022

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
0 votes
Pulkit Vaid _ Fueled April 25, 2022

Edit ^^ : pipeline logs were formatted

Suggest an answer

Log in or Sign up to answer