What is the best way to manage Audit tracking and closures in the Confluence?

[Jas S.]

Am going to share below how we started using Confluence and ended up with a web of not so connected confluence pages. Am looking to seek help on better integrating these pages, and having my team add information only once. Appreciate your help to make this process more efficient, and at same time allow executives to see detailed view from Confluence.

We started using Confluence to capture simple table of Audit findings (issues) on a confluence page, tagged owners for those and would put status as Open, Execution, Closed etc. But as discussions started, and there were documents shared for each finding, we created a sub page for each finding. Now users had to enter information twice.

Further to track daily logs of people working and adding these findings, another set of pages were created for each project, to capture the daily logging of observations.

There must be a better way to integrate these. Am thinking if we need JIRA as backend integration now to easily track findings (issues). And then just create templates to pull the reports from Confluence  - online as well as download in predefined formats for executive summary.

[Aron Gombas _Midori_]

To me it sounds that Jira could a better tool to handle this.

One audit finding is one issue (use a special issue type), discussions are comments on the issue, assignee and state changes are native issue features, etc.

Then you can use every sort of Jira reporting options (gadgets, apps, etc.) to compile an executive summary.