I know this is old but it seems like it is still a common issue and I have developed a workaround using Jira automation to call out to Power Automate. I think it could be possible within the Jira automation directly using web requests without needing Power Automate, but I'm not sure how clean it would be.
For my scenario, I wanted to generate documents in SharePoint that relate to the issue and then link the documents back to the Jira issue as remote links.
Here is the high level workflow I used:
1. Jira automation called "Generate Documents" that a user would run from the issue when they are ready.
2. The automation calls an HTTP request trigger in a Power Automate flow passing in the Jira issue.
3. The Power Automate flow does all the magic of getting more details from Jira through the API, creating a folder structure, creating documents, etc.
4. For each document that gets created, I use the API (Issue remote links) the check to see if there is already an existing remotelink with the same name to avoid creating duplicates, and if not, I create a remotelink to the document.
Like I said, if you don't care about checking for duplicates or have complexity around creating the documents, you could probably just use a step in the Jira automation itself to call the API and create the link.
I also saw mention of needing the JSON object format to create a remotelink. To find it, I basically created a new remotelink, queried it with the API to get it as a JSON object, and then simplified it after some trial and error. The API here does allow for some quirky behavior like if you format a link wrong, it still allows you to create it but it doesn't show up in the issue and can only be seen through the API call to get remotelinks.
Anyway, here is what seems to work for me. Note you will want to replace the url and title values with your own and maybe play around with the icons.
{
"application": {},
"object": {
"url": "https://link.to/the/document",
"title": "Name of the Document",
"icon": {
"url16x16": ""
},
"status": {
"icon": {
}
}
}
}Hope it helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.