Catalog
After Plans are created, product teams can create and maintain Requirements in Sanplex. Sanplex organizes requirement-related work through Epic, Requirement, and Story, which can be configured to represent different levels of product requirements.
I. Create Requirements
1. Create Business Requirements, User Requirements, and Development Requirements
In the current Sanplex interface, requirement-related work is organized through Epic, Requirement, and Story. Depending on the configured Story Concept, these levels can be used to represent Business Requirements, User Requirements, and Development Requirements.
Go to the corresponding Epic, Requirement, or Story page under Product, and click the Create button in the upper-right corner to create a new item.
Sanplex organizes Requirements through the Epic, Requirement, and Story hierarchy. Parent-child relationships and the built-in SR/sub structure support progressive decomposition, allowing teams to break down higher-level requirements into more detailed work items while maintaining clear traceability between them.
2. Split Requirements
Requirements can be decomposed through the supported requirement hierarchy.
- In the Requirement list, use the available hierarchy or split action to decompose a Requirement into lower-level items.
- In the standard Business Requirement–User Requirement–Development Requirement structure, Requirements are decomposed level by level rather than directly skipping intermediate levels.
- Parent-child relationships created through decomposition are displayed hierarchically in the Requirement list.
After opening a Requirement, its lower-level items are displayed in the corresponding child-item section, allowing you to review and maintain the requirement hierarchy.
3. Batch Create
Sanplex supports batch creation for requirement items. Open the drop-down menu beside Create Epic, Create Requirement, or Create Story, and select Batch Create where the option is available.
The Batch Create page provides multiple rows for creating requirement items together.
4. Multi-Image Upload
The Batch Create page supports Bulk upload images, allowing multiple images to be added when creating requirement items in bulk.
The available batch-create fields depend on the current requirement type and configuration.
5. Multi-Line Entry
Sanplex also supports Bulk entry. Enter one requirement name per line in the Bulk entry dialog, and the system places the entries into separate rows on the Batch Create page.
After saving the bulk text, each line is inserted into a separate row. You can then complete other fields such as Branch / Platform, Module, Linked Plan, Hierarchy, Category, and Priority as needed.
6. Edit and Maintain Requirements
After a Requirement is created, you can maintain it from the corresponding list page. The Actions column provides the operations currently available for each item according to its status, hierarchy, and user permissions.
These actions may include workflow operations, review-related operations, editing, closing, hierarchy maintenance, and relationship management.
7. Child and Linked-Object Information
Requirements can be organized into parent-child structures. The list visually distinguishes different hierarchy levels, including built-in labels such as UR, SR, and sub where applicable.
The list can also display a Linked Objects column. The value in this column indicates the number of objects associated with a Requirement.
For parent-child Requirements, decomposition follows the configured hierarchy.
- A parent Requirement can contain lower-level child Requirements.
- Parent-child relationships are maintained separately from general object-linking relationships.
- Downstream operations depend on the position of the Requirement within the hierarchy and the functions available for that requirement type.
II. Feature and Permission Configuration
1. Story Concept Settings
Administrators can configure the terminology used for the requirement hierarchy under Admin > Features > Product > Story Concept.
The Story Concept configuration defines the terms used for levels such as Epic, Feature / Requirement, and Story. Administrators can select an existing concept configuration or use Set Story Concept to maintain the available concepts.
2. Enable Requirement-Related Product Features
Requirement-related Product features can be enabled under Admin > Feature Options.
For example, the Product module provides optional features such as Requirements and Epics. Select the required options and click Save to make the corresponding features available in the Product module.
3. Permission Settings
Requirement-related permissions are configured through the system permission groups rather than through separate Business Requirement, User Requirement, and Development Requirement permission pages.
Go to Admin > Users > Permission, and use Assign Permissions by Modules to configure permissions for the relevant module. For example, selecting Story displays the available Story permission sets and methods, such as viewing, managing, importing or exporting, deleting, reviewing, creating, and editing Stories.
Different permission groups can therefore be granted different levels of access to requirement-related functions.
III. Switch Views
Requirement-related lists support different display modes for reviewing work items and their hierarchy.
On the Story page, use the view toggle in the upper-right area of the list to switch between the available list and hierarchy-oriented views.
- A hierarchical view is useful for understanding parent-child relationships and requirement decomposition.
- A flat list is more convenient when searching, filtering, sorting, or reviewing item attributes independently of the hierarchy.
IV. Link Requirements to Plans
Plans can be used to organize requirement-related work. In the current Sanplex interface, Stories can be linked to a Plan and reviewed from the Plan details page.
Open a Plan and select Linked Stories to view Stories already associated with that Plan.
You can also link Stories directly from the Plan List. In the Actions column, click Link Story for the target Plan.
On the Link Story page, select the Stories you want to associate with the Plan, and then click Link Story.
V. Link Any Requirement
Parent-child decomposition and general Requirement relationships serve different purposes in Sanplex.
- Parent-child relationships represent hierarchical decomposition between requirement levels.
- Linked Objects can be used to establish additional relationships between related items without changing their parent-child hierarchy.
To create this type of relationship, open the Requirement item and use Linked Objects on the details page. Related objects can then be added and viewed from this panel.
This makes it possible to maintain relationships between related Requirements or other supported objects even when they do not belong to the same parent-child structure.
