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

issue with automatically creating different and multiple Issue Macros in confluence page


I have a Listener in ScriptRunner that based on the create version event in JIRA it triggers the creation of a Confluence page containing several issue macros with different types of information. 

Let's assume I have 3 issue filter macros that are created using wiki markup once the Confluence page is created .

The issue is that once the page is created, the 3 tables contain only the values of the first table (so basically the other 2 tables shows the data from the first table even though if I edit the 2 macros from page edit, the correct filter appears in the macro browser). 

This might be a cache issue, but I not sure how I should proceed. I already added the cache parameter to false: 


{jiraissues:anonymous=false|url=" + url + "|columns=type;key;summary;due|title=" + jiraIssues.get(i) +"Dates|cache=false}


Can you please help?

Thank you!




2 answers

This functionality was also reported by Atlassian confluence support team. It seems to be an already documented bug: CONFSERVER-52556 - Multiple JIRA Issues Macros inserted via markup are showing the rest of the first JQL

I found out that there was no issue with the ScriptRunner listener. Issue was solved by using Confluence storage format instead of Confluence wiki markup when creating the 3 filters on the Confluence page. Using Confluence storage format, the filters are refreshed correctly. 

My conclusion is that there is an issue from Atlassian when creating multiple macros using the wiki markup in Confluence. 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events