Is the Product Requirements template better suited as a comprehensive set of system requirements, or is it more effective to create a Product Requirements page per feature for a reasonable sized project?
I like the idea of breaking out major system features into their own child page as a Product Template, but we'd also need an easy way to export all system requirements into a single document, so possibly over many Confluence pages.
I'd say do what works best for you. You can always export your pages into one PDF document by doing a space export and choosing the Custom Export option to export a subset of pages.
Hi team, I’m Avinoam, a product manager on Confluence Cloud, and today I’m really excited to let the Community know that all customers can now try out the new editing experience and see some of the ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs