How to create a static jira issue list in Confluence

[Marcel Plomp]

We are frequently using the JIRA-issue-macro in Confluence to show a list of issues over a period. 

After adding the macro to a page it must be static "forever", meaning it must not change when refreshing the page, after editing and when pushing the refresh button at the end of the list. 

Adding the parameter static to the resource code of the jira-issue-marco is not working. When you push the refresh button at the end of the list, the list will still be updated.

BTW: Adding the parameter to the source code is not an option for "normal" users (not being a developer). A new user macro is maybe an option but I do not know how to create/code this.

Any ideas?

[Marcel Plomp]

Copy/paste from the page with the issue list generated by the JIRA macro, is not working in IE, as IE adds a lot of blanks to each cell in the table. Using another brower is not an option as we are stuck to IE (for most common users)

The following workaround is available and acceptable:

• Find the page with the dynamic JIRA macro
• Hit the link at the bottom of the table
  25issues.PNG
• The list will open in JIRA
• In JIRA, export the list to Excel (Current Fields)
• Copy the relevant cells from the Excel file
• Paste the cells on the page where you need them

The only thing that stays dynamic on the page is the link to the JIRA issue. All other cells are plain text.

Workaround as described is  based (for us)on standard functionality in JIRA and Confluence and availability of programs like MS Office.  

[Bob Swift]

There are a few techniques you could use.

1. Use JIRA Command Line Interface (CLI) and getIssueList to produce a static csv file that can be included on a page using the CSV Macro. There is an example on a Confluence page here: getIssueList
2. A more general solution is to capture a point in time of a dynamic page. In this case, just using the standard JIRA macro. See How to archive pages with dynamic content

[Marcel Plomp]

Actually, we do not want another (paid) plugin, at least not one with a lot of functionality that we are not going to use initially.

[Marcel Plomp]

Unfortunately this will not be fixed.... https://jira.atlassian.com/browse/CONF-36155