Hi,
I am working on an automation in Confluence to save a page that includes dynamic lists of "Jira Work Items." The goal is to capture the content of the page at a specific date, ensuring it remains static and does not update automatically like the "Jira Work Items" typically do.
I am open to any suggestions for the method of capture, whether it be via email, storing it somewhere in Confluence, or in Microsoft OneDrive.
Do you have any suggestions on how to achieve this?
Great question, I can see how during the life of a project for example you want to capture the state of Jira issues at a specific point in time to reference later. I have no idea how you can do that but am interested in seeing what others suggest.
Hi @Houcem Hedhly -- Welcome to the Atlassian Community!
Where is your specific date stored: with each work item or with the page content?
If with each work item, have you considered storing the data in an entity property, making it more difficult to tamper with?
If with the page content, you could include that specific date in the page content.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bill Sheboy
Thank you for responding.
In my initial post, when I said, "The goal is to capture the content of the page at a specific date, ensuring it remains static and does not update automatically like the 'Jira Work Items' typically do," the "it" refers to the content of the page, not the date. For the date, I am using a cron job that will run once a week at a specific day and time.
Kind regards,
Houcem
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you mean you want to capture the data from a set of work items at a point in time, and store that as content on the page?
One way to do that would use either the Lookup Issues action or the REST API to capture the work item data, and then store those present values on the page content using the REST API>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.