The Product Requirements blueprint helps you to define, scope and track requirements for your product or feature.

The first time you use the Product Requirements blueprint in a space, Confluence will create an index page and add a shortcut on your space sidebar (shortcut only available in the default theme). The index lists all the Product Requirements pages in that space, and displays a summary of the information on each page (such as status and owner). You can have as many Product Requirements pages as you need.

Related pages:

To use the Product Requirements blueprint:

  1. Choose Create > Product Requirements to create a Product Requirements blueprint page
  2. Enter information about your product or feature – the instructional text will prompt you.

You can @mention team members to bring them into the conversation about the page.

Screenshot: Index showing a series of Product Requirements pages and summary information

Screenshot: Editing a Product Requirements page

The Product Requirements blueprint uses these Confluence features:

  • Page Properties and Page Properties Report macro - content that you enter within the page properties macro can appear on the index page.
  • Instructional text  - this handy text prompts you to enter information or create a JIRA issue and disappears when you start typing or view the page.
  • Mentions - @mention a user on the page and they will be notified in their workbox.

Customising this blueprint

As no two products or projects are alike, you can customise the templates that are used by the Product Requirements blueprint - see Customising the blueprint templates.

You might choose to edit the index page in a space to change the columns to be displayed by the Page Properties Report macro.

You might choose to edit the page template to:

  • edit the headings or add additional headings
  • change the instructional text that prompts users to enter information to suit your context
  • add or remove rows within the Page Properties macro.

See Instructional text to find out more about using instructional text in templates. 

  • No labels