Automated page, with jira tickets, needs to become static page with no subsequent updates

Question

I've got bi-weekly and Monthly report pages being created, via automation in confluence. It essentially shows the work completed over the previous period. Also updates on open risks etc...

I need a way for the new page, and the /Jira macros to remain static after it is created, to allow for an audit log of progress over time. Any guidance on the macro or JQL filter or 3rd party product which would allow this ? Is there such a thing as a "run once" ?

Barbara Szczesniak · Answer

@Nigel Mitchell Since the point of the Jira macro is to provide a view of the current state of the tickets when viewing the page, you would indeed need a way to create the page without using this macro.

When using the macro, I would think that the only way to capture a static view of the page would be to:

* export the page to a PDF (not sure if this works with Jira data or may require a 3rd-party app) or
* capture an image of the page (or the part of the page showing this data)

I'm not sure if you can automate the export or the image capture. If you then, attach the PDF or image file to the page (add a description when uploading), you will have a record of the state of the page each time you generate such a file (for example, you might have attachments for when created, week 1, week 2, week 3, or whatever convention makes sense for you).

Anatolii Starshekov _Wombats Corp_ · Answer

Hi, @Nigel Mitchell

As I understand your query, you may implement something like that via user macros. However, the approach won't stick to Jira permission settings, i.e. the data in the user macro may become visible to all macro users.
Does that suit your needs? Could you please elaborate on that?

Lucas Modzelewski _Lumo_ · Answer

check this: https://support.atlassian.com/jira/kb/how-to-create-generic-table-with-ticket-data-in-multiline-text-field-using-automation/

I used a similar approach to review support requests.At first, I reviewed all tickets from a specific period (e.g., 2 weeks) to provide feedback on completed issues and offer tips on unresolved ones.Later, I focused only on tickets that were still open or unresolved.

I was using this in a Jira ticket, but it will probably work with Confluence as well.