Product Backlogs are means to collect user stories.
Create a backlog to collect user stories. You may organize user stories in different backlogs, although it is usually more effective for agile teams to stick with only one.
Backlogs aggregate prioritized user stories. Usually it is not a good idea to work with different backlogs, since this makes it difficult to define a clearly prioritized list of topics to work on. Therefore the main purpose of the Product Backlog Doctype is to define multiple views on the work. We expect that users work with their backlog on JIRA anyway. Backlogs provide views and allow to add additional information that is relevant for a group of related units of work.
The document type product backlog provides the following properties:
Please note that only information about specific properties is provided here. Common document property used by all document types are documented by Document Properties.
Add references to information on external systems here. Probably this is an issue on your JIRA server.
Provide an introduction to set the context of the product development.
Each document type has child document support, so does the Product Backlog Doctype.
Usually this is not used, since you can build hierarchies with User Stories themselves.
List the stories in the backlog. If this is a view on stories of the team backlog, do not add stories as subdocuments to the backlog document. Use a query and select the stories to be displayed in this view by their properties.