Product Backlogs are means to collect user stories.
Description
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.
Properties
The document type product backlog provides the following properties:
Reference
Add references to information on external systems here. Probably this is an issue on your JIRA server.
Sections
Description
Provide an introduction to set the context of the product development.
Subordinate Backlogs
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.
Prioritized Stories
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.
Notes
These are internal notes that are usually not exported and only visible to team members with write access.
But this is not a safe place to store sensible information. It is just a convenience for the reader to not be bothered with notes stored here for the authors for later use. The security level is about suppressing the representation by a CSS style. Therefore consider this as a convenience for the reader, not as a security tool.
References
For a document the references section contains pointers to resources that prove the statements of the document.
Often these proofs are not easily distinguishable from further information. In this case you may want to skip the reference section in favour for the resource list.
Resources
The resources section provides references to further information to the topic of the document.
This may be information on the internet provided by the resource or information in the team's information systems. Anything the reader of the resource might want to know, may be listed here.
