Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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

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.

1 comment

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.


Log in or Sign up to comment

Atlassian Community Events