Confluence's Product Requirements Blueprint helps you to define, scope and track requirements for your product or feature.
A workflow is added to the Product Requirements Blueprint to help a team manage the content workflow. Once a Space administrator attaches a workflow to this Blueprint, each time the page is edited it requires approval from one of the stakeholders. When all stakeholders have approved the content, the document automatically moves into a new state.
For example
Instead of manually updating the Document status field when content is updated on the Product Requirements Blueprint, the workflow manages updates it automatically.
Watch this short video to learn how workflows automate the product requirements process.
Working with the Product Requirements Blueprint
- Click Create then select the Product Requirements Blueprint from the list.
- Click Create. The Blueprint is added to the Space. Workflow instructions may appear at the top of the page.
Enter the Target release and Theme fields, and assign Document owner, Designer, Developers, and QA roles.
These fields are required for the workflow.
- Click Accept for the For Review state in the Workflow
window to move the workflow into the approval stage when the content is ready for Development and QA review. A workbox notification is sent to the user assigned to Development and QA roles. Each time the workflow moves forward the Product Requirements page properties are automatically updated.
See the Product Requirements Blueprints instructions for more information.
