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