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

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

CircleCI Error: unknown association

We are trying to integrate CircleCI with Jira Deployments. We run the following command in our .circleci/config.yml file:

 - jira/notify: 
    environment: << parameters.environment >>
    job_type: deployment
    token_name: CIRCLE_TOKEN_FOR_JIRA


And get the error:

This job is passing, however another job in workflow is running
Update Jira with status: successful for 174
Results from Jira: 
ERROR: unknown association
  "acceptedDeployments": [
      "pipelineId": "xxx",
      "environmentId": "xxx-dev",
      "deploymentSequenceNumber": 174
  "rejectedDeployments": [],
  "unknownIssueKeys": [],
  "unknownAssociations": [
      "associationType": "serviceIdOrKeys",
      "values": [


2 answers

I'm having the same issue...

Please try to provide a valid `issue key` or `service id` to `associations` (In most cases, you would want to use issue key), which will be the only bridge between circleCI and Jira.  You provided empty string as association.


This association is used to associate deployment information with issues. If you send deployment with invalid association to Jira, Jira wouldn't know where to use this information. That's why with invalid association value, Jira can't know what to do with it.


Thank you.


MJ Kim

DevOps team, Atlassian

I'm getting the same error.  Reading the orb details it should error:

echo "No Jira issue keys found in commit subjects or branch name, skipping."

but it doesn't. 

It successfully calls Jira with an empty key. 

Is there some way to get the key from the GITHUB PR title/body?  I don't like the idea of having to force developers to tag commit or branch name as well as PR .

Hello folks, 

Could anyone experiencing this issue provide more information about their usage?

  •  Share an example Issue ID so that we may check its pattern
  • What is the branch name in the failing occurrences?
  • Does this work some of the time or is this a constant issue?


The Issue ID must be located in either the branch name or the commit message (subject). We are looking into feedback there may be an edge-case related to tagged commits that experience this issue.


We have just tested the integration and did not replicate the issue. This has us thinking the issue may be around a bad regex pattern for the issue IDs or possibly the issue IDs not being picked up for another reason we are hoping to discover.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Apps & Integrations

🍻🍂Apptoberfest Update: Upcoming Virtual Events 🎉

Hello Community! I hope you've been enjoying the 🍂Apptoberfestivities🍂 (I know I have!) The event is heating up next week with a series of virtual events that we're calling the 🍻🍂Partner App ...

427 views 3 18
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you