Is there a Smart Value for Issue Remote Links?

[Andrea_Lawrence]

I'm looking for a way to access info related to remotelinks on an issue without having to do API calls and text manipulation. These remote links are NOT issue links.

I have several jira automations for handling issues of a certain type. When this type of issue is created, an automation runs that does the following:

1. modifies some custom fields on the issue
2. creates a wiki page
3. creates an issue in a different project
4. adds content to the wiki page created in step 2

The first problem I've noticed is that when using the "Create page in Confluence" automation action, there's not an option to automatically link the created page to the trigger issue. So I have to either manually link the page after the automation runs or include additional API calls to link the wiki page. (How to link a Confluence page on a Jira Cloud Issue via Rest API )

I have a manual automation that will add content to the created wiki page using an input variable for the page ID. However, I'd like to have the manual automation add content without requiring an input value.

Confluence pages linked to Jira issues are added as remote links. I haven't been able to find any smart values that would return remote link values tied to an issue so to do this I had to:

1. API call to get the remote link (Get Remote Issue Links)
2. remove part of the url string to get the page Id
   1. {{webResponse.body.get(0).object.url.remove("{{baseURL}}/wiki/pages/viewpage.action?pageId=")}}
3. API call to get page details (Get Page by ID)
4. API call to update wiki page (Update Page)

This seems excessive with unnecessary steps to get remote links tied to an issue.

The remote links are also not included when exporting issue data.

[Armin Meyer _Seibert - Coderay_]

If an additional App is an option for you. We developed an App called AutoPage that covers this. 

Autopage automates rule based page creation from Jira issues and sets a link between Jira and Confluence automatically. Beside of this you can use templates for the page creation that contain the definition which information from the Jira issue should be shown in the created Confluence page.

The app is fully integrated with Jira automation. So you can use the full power of automation with it.

In your case you replace the step of creating a wiki page with automation. Instead you trigger the AutoPage Rule with Automation and you get a page that is linked, styled, prepoulated and in sync with the Jira issue.