What is the recommended way for subdividing system requirements into Confluence pages?

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.

Thoughts? Thanks.

2 answers

1 accepted

0 votes
Accepted answer

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.

See docs at https://confluence.atlassian.com/display/DOC/Exporting+Confluence+Pages+and+Spaces+to+PDF

Do most people just put all of their system requirements in one Product Requirments page?

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Feb 06, 2019 in Confluence

Try out the new editing experience

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 ...

821 views 40 5
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you