Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Confluence Gliffy diagram returns 404 when accessed in a Jira(plugin)

I am developing a Jira plugin and my plugin wants to access a publicly available Gliffy diagram image, the url provided in embed dialog works when accessed via browser but when access using a java api it returns 404 file not foundg1.png

It has a work around though, but you have to know the attachment id of the and use another rest api to get attachments instead which can be found in the network tabs

{$confluenceBaseUrl}/download/attachments/{$attachmentId}/{$attachmentName}?version=2&modificationDate=1672036000760&api=v2 when embedding to a jira Issue

Alternative API usedgliffy2.png

its such a pain in the neck work around especially when you have a lot gliffy diagrams to embed.

has anyone experience this? thanks :D

1 comment

Hi @Gen Gulay !

If Deepak's suggestions don't help you solve this, please feel free to email our support team at

Our PM might be curious to hear more about how you're using Gliffy between Confluence/Jira + your needs within this use case. Would you be willing to have a convo with him? I'd be happy to make an introduction! :)


Like gen gulay likes this

hello, it seems that it was a fault on our end, issue is resolve now thanks


Log in or Sign up to comment

Atlassian Community Events