Logs settings
Overview
As per Atlassian’s guidelines, all marketplace apps are supposed to be migrated to Forge. Which means, no customer data is stored on our servers, but it remains on Atlassian’s cloud infrastructure.
In terms of ARNR logs, previously, we stored all the customer release notes and reports attachments on our servers for 90 days. However, now, as per the Forge guidelines, even these attachments are not supposed to be in our infrastructure, and to support this, we have introduced a new enhancement that stores the release notes and report attachments on the customer’s Jira instance, which means it remains under Atlassian’s infrastructure. Let us check how this works.
Log settings
As a Jira admin, go to Jira settings () >> Marketplace Apps >> Click on Automated Release Notes & Reports section in (Left navigation)>> Logs settings tab >> Select the project where you want to store logs >> Click on Save.
While setting this up, choose a stable Jira project that won’t be removed. Deleting the project or related ARNR-created work items will permanently erase stored rules execution log data. A dedicated, limited-access project is recommended.
Once this is done, the system automatically creates a new work item in the selected project, and all the attachments created upon ARNR’s rule execution are attached to this work item. Search for ARNR system issue – Logs & attachment storage in your Jira, and you will find this system-created work item.
These attachments are stored
What happens to ARNR’s existing Logs tab?
The existing Logs tab of ARNR in-project or cross-project screens remains as it is, and it will function as before. The only change is that when you click attachments like PDF, MS Word, PowerPoint, etc. are accessed and retrived fron the system-created Jira work item mentioned above. Which means the data is now not stored in our infrastructure.