You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi all, I'm asking for suggestions, ideas and brainstorms related to documenting / tracking / relating many products and their many, many features in Confluence.
Essentially, we need to document which products do or don't have which features, and if they do, link(s) to the documentation that provides more detail. The scale we are talking about is, say 250-350 individual features and 150 products.
To date this group has been using a very large Excel workbook, with features as rows and products as columns, and text in the individual cells.
Some of the options I can think of include,
I suspect that this situation really requires a relational database, but I don't have a good solution or option there yet.
Ideas? Examples? Brainstorms???? Thanks in advance for your thoughts.
Hi @Anna Dziubańska for the time being I have been using the Page Properties & Report macros. This is indeed generating a list like I intended but there are a couple of drawbacks.
It might be possible to generate a more sophisticated listing by using ServiceRocket's Scaffolding, LiveTemplate and Reporting add-ons. Scaffolding can add metadata to pages; LiveTemplate keeps data entry consistent across pages, and Reporting can generate reports using the metadata. I hesitate to use this more complicated solution right now, but it could probably work.
Let me know what direction you go in, too!
We've tried the scaffolding app (mainly because we would like to use live template), but unfortunately it doesn't work with page properties report and the workaround they proposed in one of the help sites does not work as we expected.
We are currently using Table Filter for Confluence by Stiltsoft to work together with page properties report - it allows you to sort/filter by multiple columns
We have not fully set up the solution though - as I'm a bit worried about the size of the page properties report (ours would have ¬300 rows) - we've only tested it on around 30
Hi @Anna Dziubańska and @Michelle Rau good ,
I'm from the Stiltsoft team and the Table Filter and Charts for Confluence app is one of our add-ons.
We confirm that the app works with the Page Properties Report macro perfectly well - you may check here for the use cases.
The 300 rows is not a limit for our macros, they support thousands of rows. To make such big tables readable, use the pagination feature inside the Table Filter macro.
Maybe a short 30-minute live demo will be interesting for you and your colleagues? Please book your time and we'll be glad to answer all your questions regarding aggregating tables, collecting data and amplifying standard Confluence reports.