Clone Work item does not have an option to copy over confluence links and linked pages to copy over in automation screens. Anybody achieved this?
You're right that Clone work item doesn't bring Confluence page links / remote links across — those aren't in the clone options today. Two workable patterns: 1) If the Confluence URL lives in a custom field or the description, turn on that field in the Clone action (or Edit work item after create). That's the simplest path when the link is stored as data. 2) If the pages show under the issue's Linked pages / web links (remote links), copy them with Send web request after the child exists: - GET `{{baseUrl}}/rest/api/3/issue/{{parentKey}}/remotelink` (Authorization: use the rule actor; Accept: application/json). - For each result that looks like a Confluence link, POST the same JSON body to `{{baseUrl}}/rest/api/3/issue/{{childKey}}/remotelink`. Use a Created work item / Issue linked (child) trigger so `{{issue.key}}` is the child, and keep the parent key in a Created variable from `{{issue.parent.key}}` or from the trigger fields. Test on one issue first and check the audit log for 401/403 — the rule actor needs Browse + Edit on both issues. Issue links (blocks / relates to) are separate from Confluence links; those have their own Clone checkbox and won't move the Confluence pages. Happy to sanity-check a rule screenshot if the remotelink copy fails on the first try.
@Janani Venkateswaran
In addition to what @Integration Yard mentioned, I would go with #2 approach. By default, Linked pages/weblinks copying from Jira issue to issue are not available out of the box - event with standard automation for Jira rule setup.
One of the things that we always try to follow is not to duplicate objects (i.e. attachments/links) from the parent issue down to its child issues as much as possible. It is because keeping the source of truth as the goal. I can also see your reasoning for duplicating the object in the child issues, so one don't have to keep going to the parent issue for the information.
I would also recommend you to contact Atlassian Support (https://support.atlassian.com) for their suggestions as needed.
Hope this also helps.
Best, Joseph
Hi @Janani Venkateswaran
In Jira Automation, standard issue-to-issue links can be copied natively, but linked Confluence pages and web links are stored as Remote Issue Links (remotelink). The built-in Clone work item and Link issue actions do not support copying remote links out of the box.
remotelink
To achieve this, you can use the Jira REST API via the Send web request action in Jira Automation. This approach uses a two-step web request flow:
GET
POST
{{issue.parent}}
{{triggerIssue}}
{{createdIssue}}
Add a Send web request action:
{{baseUrl}}/rest/api/3/issue/{{issue.parent.id}}/remotelink
Authorization
Basic <API_TOKEN_BASE64_ENCODED>
email:api_token
Accept
application/json
Because an issue can have multiple remote links (or a mix of Confluence pages and external web links), use an Advanced branching action to iterate over the returned links:
webResponse.body
remoteLink
Inside this branch, add another Send web request action:
{{baseUrl}}/rest/api/3/issue/{{issue.id}}/remotelink
Content-Type
{ "globalId": "{{remoteLink.globalId}}", "application": { "type": "{{remoteLink.application.type}}", "name": "{{remoteLink.application.name}}" }, "object": { "url": "{{remoteLink.object.url}}", "title": "{{remoteLink.object.title}}", "summary": "{{remoteLink.object.summary}}", "icon": { "url16x16": "{{remoteLink.object.icon.url16x16}}", "title": "{{remoteLink.object.icon.title}}" } } }
I hope this helps & resolves your issue. 🙂
Thanks, Anwesha
Hi @Janani Venkateswaran,
Anwesha's GET and POST round trip works. I ran the REST calls on a test site today, and the child's link came back with the same globalId and application type com.atlassian.confluence as the parent's.
1. Copy only the Confluence links in that branch. A plain web link has no globalId, so her body sends "globalId": "" for each one, and Jira updates the link that already has that globalId instead of adding a new one. On a test issue the second web link overwrote the first. Add a condition first inside the branch: {{remoteLink.application.type}} equals com.atlassian.confluence, where remoteLink is the variable name from her step 3.
2. Wrap the values in jsonEncode. A quote in a page title breaks the JSON otherwise:
{ "globalId": "{{remoteLink.globalId.jsonEncode}}", "application": { "type": "{{remoteLink.application.type.jsonEncode}}", "name": "{{remoteLink.application.name.jsonEncode}}" }, "object": { "url": "{{remoteLink.object.url.jsonEncode}}", "title": "{{remoteLink.object.title.jsonEncode}}", "summary": "{{remoteLink.object.summary.jsonEncode}}" } }
https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/
3. {{issue.parent.key}} works for a task or story under an epic too. The smart values page still says sub-tasks only, but on a team-managed project it gave me the epic's key for both.
The account behind the API token needs Browse projects and Link issues on the child's project:
https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-remote-links/
I haven't run the whole rule end to end, so check the audit log after the first child.
{{issue.key}}
childKey
{{createdIssue.key}}
/rest/api/3/issue/{{childKey}}/remotelink
{{remoteLink.application.type}}
com.atlassian.confluence
Authorization: Basic
Keep the globalId from the source link in the POST body. That way Jira still recognizes the link as a Confluence page, not as a plain web link.
globalId
It looks like you're new here. Sign in or register to get started.