Jira Automation: Linking a Confluence page with Jira issues

[#1]

This article helps build a solution using Jira Automation and Confluence REST API to link a newly created Confluence page with a Jira issue.
For instance, When a confluence page is created using Jira Automation, the page link should be added to the Jira issue.

Adding the Confluence page link into the Jira issue.

This can be done using the Create or update remote issue link API endpoint, here's an example of the request:

URL: https://<SITE_URL>/rest/api/3/issue/{{issue.key}}/remotelink
Method: POST

Web request body:
{
 "object": {
        "title": "{{issue.key}} {{issue.summary}}",
        "url": "{{createdPage.url}}"
           }
}

Headers:

• Accept: application/json

• Content-Type: application/json

• Authorization: Basic <encoded Email:APIToken>
  For more details on how to encode the credentials, please check this article: Automation for Jira - Send web request using Jira REST API

Alternatively, you can add the smart value that includes the page URL in a comment or a field:

{{createdPage.url}}

Illustration:



Thank you for reading and Happy Automation! 

Other related articles:

Jira Automation: Updating a Confluence page with information from Jira issues

[Carlos Adrián Peréz Díaz]

Hi, I'm basically trying to link a confluence link into a jira issue via automation as well. I have followed all the steps as described above, however I'm getting the following message:

ERROR 404

{
  "errorMessages": [
    "Issue does not exist or you do not have permission to see it."
  ],
  "errors": {}
}

I've permission and access and edit the Jira issue. Any clue where the error could be? 

Thanks in advance.

[Ralf Rutke]

Hi,

as I have spent some hours with reading and trail an error, here are some hints:

• The error message above happens due to missing permissions. 
  You need to follow the guidelines in Automation for Jira - Send web request using Jira ... - Atlassian Community to create an API-Token. That means: a) Go to  https://id.atlassian.com/manage-profile/security/api-tokens. Create the API-Token b) Base64 Encode it for example by using tool like Base64 encode. The String to encode ist "your@mail.com:API-Token": c) copy the Base64 encoded String to you clipboard.
• The Illustration above doesn't show the necessary header-Fields, that you need to fill
  
  Important are the Headers:
  - Accept
  - Content-Type
  - Authentication - Here you need to enter "Basic Base-Encoded-String"

It might be the case that most of the people here don't need that description. Anyway, it's for the rest like me :-)

[Miguel Santana]

The same problem happens to me, and in addition to the steps described in the previous post, I solved it by adding .urlEncode as part of the smart values inside the brackets.

Example:

https://<Site_URL>/rest/api/3/issue/{{issue.key.urlEncode}}/remotelink

Hope it helps.