Automatically link the URL of a Confluence page to a Jira issue and vice versa.

[Schuuudi]

Hi there, 

I have created an automation where I automatically create a Confluence page from a newly created Jira issue. Now I want to automatically link the Confluence URL in the Jira ticket using ‘Link Confluence Page.’ Afterwards, I also want the Confluence page to be automatically linked to the Jira ticket.

I am not a developer, and I have spent hours researching how to implement my idea using the ‘Send web requests’ automation – unfortunately, without success. Can someone give me an advice?

Thanks in advance :-) 

[Abel A]

Hi, 

I used this endpoint. https://[yoursite].atlassian.net/rest/confluenceIssueLink/1/confluence?issueId={{issue.id}}&pageUrl={{createdPage.url }}. Takes some time (2~10 minutes) for cloud to index the link. The link is created right away but based on my experience it does not open right away. 

[Hans Polder _Devoteam_]

It would be so cool if this works! I was trying it as well with the webrequest but for the life of me I couldn't figure out what to do with just the {{createdPage.url}} as output.

If your experience is that the URL might not work right away, in Cloud there is since very recently a 'Delay' option added, which would help avoid issues:

[Schuuudi]

Good morning and thank you so much for your reply! 

I am still testing it - so far without success with or without delay. . . 

@Abel A How can I imagine the result of this query? What should I see where, once it's successful?

[Abel A]

Hi @Schuuudi , 

In your automation audit log, it will say "Successfully published web request".

[Fabian Fischer]

I used the same web request configuration, but I'm encountering an issue where the API endpoint returns a 401 when using the Personal Access Token (Base64 encoded) in the Authorization header with the Basic Auth schema.

When inspecting the request made by the browser when adding it manually, I noticed that authentication is handled using a tenant session token in a cookie.

Has there been a recent change to the authentication mechanism, or am I overlooking something in my request setup to the API?

In the screenshot, the "Continue when request response is not 200" option is enabled. This prevents the error from being displayed but doesn't actually resolve the issue.

[Bill Sheboy]

Hi @Fabian_Fischer3 -- Welcome to the Atlassian Community!

As this is a very old thread, please create a new question (perhaps adding a link back to this one).  That will ensure the maximum number of people see it to offer suggestions.

When you post your question, remember to include:

• an image of your complete rule in a single image for continuity
• images of any relevant trigger, actions, conditions, and branchings
• an image of the audit log details showing the rule execution (with all areas expanded)
• explain what is not working as you expect and why you believe that to be the case

Kind regards,
Bill

[Lisa Forstberg]

Hi @Schuuudi ,

Yep, it seems like the automation is still limited in this area. I would love to see some movement on the jira<>confluence automations as I have a similar need for Post Incident Reviews in my current assignment. 

Some workarounds have been suggested: 

• Creating a URL custom field in Jira and sticking the Page URL in this field instead of the standard linking behaviour - see here
• Sending a webrequest (not accepted answer though) - see here

best regards

/L

[Schuuudi]

Hi @Lisa Forstberg 

I appreciate the confirmation that there are obviously still gaps here - that doesn't make me feel quite so stupid ;-)

I have already read a few posts on this and will now follow up on your last tip.
Thank you :-)