Attachment Access in Jira Automation

[Eitzaz Haider]

Dear All,

I am trying to get all attachments (images) inserted in table of description field of work item but it not showing any images or attachment and secondly there is a huge gap between description and other fields i am rending html in email 

{{issue.description.html}}

any suggestion pls

[David Freitez]

Hi @Eitzaz Haider ,

Can you provide further information of what you are trying to achieve?,  screenshots of what you are expecting to collect from the Issue description.

Regards,
David

[Eitzaz Haider]

@David Freitez thank you for your response. I am trying to share ticket details along attachment through email using jira automation, all content (table, etc) rich format data shared with users except attachments inside table. table in description has images as attachments but those are not displaying. Got my point?pls see screenshot

[Darryl Lee]

Hi @Eitzaz Haider 

Unfortunately images in Descriptions and Custom Fields that allow images are referenced (at least using the regular API) like so when converted to HTML:

    "description": "<p><span class="image-wrap" style=""><img src="/rest/api/3/attachment/content/10137" alt="ThisIsFine.png" height="352" width="700" style="border: 0px solid black" /></span></p>",

So if I were to put the full Description/Field in an email (which it looks like you did), the included image would have a URL of:
https://MYSITE.atlassian.net/rest/api/3/attachment/content/10137

Unfortunately most mail applications don't support being "logged in" as a user.

So what happens is your mail app tries to get the image, https://MYSITE.atlassian.net/rest/api/3/attachment/content/10137, doesn't have permission, and so it displays a broken image.

Recently Atlassian announced the ability to include attachments with Emails from Automation. Unfortunately these attachments can only exist within the Automation Rule. 

I did notice that the new Enhanced email customization abilities allows for inserting Images via URL, so I tried this:

But {{issue.attachment.first.content}} again expands to https://MYSITE.atlassian.net/rest/api/3/attachment/content/10137 and so I got a broken image in my test.

Anyways, the real problem here is that these links to attached images require authentication, and it doesn't look like the Email action in Automation will do the work of downloading an image and hosting it somewhere "public" to be included.

Ideally the "Add Attachment" functionality would allow you to specify Issue Attachments and allow those files to be referenced in the email. (Because also, I don't think the current implementation would allow you to use an attachment in say, a header or logo, but rather it would just show up as an attached file to the email.)

[Eitzaz Haider]

Thank you for your well detailed explaination. Yes you are correct attachment access binds with permission and even you got attachment access links but jsm also check the permission but my customer wants to get all without logging :), i will update once i found alternative solution