How to create a static list of Jira issues in confluence page?

[Eric Blair]

I will be creating Confluence Release pages to list the issues in Jira which are to be in a release. Once this page has its list, it must keep them without changing because people may refer back to it later and see what issues went out with what release. Yes, I can do this manually, but I found that Confluence can tap into Jira issues through this macro:http://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro

However, that macro seems to be based on having a Jira filter created, which means that for each release I would need to create a Jira filter and paste the macro into the new release page. So I would like it to just import the Jira isses columns one time and not refer back to the filter. Later I can change just the filter and get the new list for a new release.

If what I ask is not possible with that macro, is there some other non-manual way of doing this?

[Bob Swift]

Use JQL in the JIRA issues macro instead of a filter. Do your query in issue navigator then view -> xml for the JQL based url. If you need to freeze the page result permanently even if the JIRA items associated with the release are changed, then that can be done as well.

[Eric Blair]

Thank you for the quick reply Bob! How is it that one freezes the page result?

[Trevor Hunt]

Bob, how woudl you go about freezing a result as you indicated in the above comment?

[Bob Swift]

Well that was bad. I missed Eric's comment not to mention not providing more details originally. Sorry about that :(. I was referring to How to archive pages with dynamic content.

Update: this requires a JIRA issues macro that produces a real table as output - there seems to be different results produced by various JIRA issues macro versions or parameter settings. Otherwise, you would have to use SQL macro against the JIRA database to produce a table that could then be archived.