Product
1. Using Sanplex by Role
1.1. Administrator
1.2. Program Manager
2. Introduction of Sanplex features
2.1. Core Management Framework
2.1.1 Program
2.1.2 Project
2.1.3 Product
2.1.4 Execution
2.1.5 Management Models
2.2. Dashboard
2.2.1 Getting Started with Tutorials
2.2.2 Quick Add
2.2.3 Notification Center
2.2.4 Effort Tracking
2.2.5 Dashboard - Project and Execution
2.2.6 Dashboard - My Work, Contribution, and Recents
2.2.7 Dashboard - Approval
2.2.8 Contacts
2.3. Program
2.3.1 Program List
2.3.2 Program Kanban
2.3.3 Create Program
2.3.4 Create Sub-Programs
2.3.5 Project Charter Management
2.4. Product
2.4.1 Create Product
2.4.2 Manage Modules
2.4.3 Multi-Branch and Multi-Platform Management
2.4.4 Manage Plans
2.4.5 Manage Stories
2.4.6 Story Reviews
2.4.7 Story Status and Phase
2.4.8 Create Releases
2.4.9 Track Progress
2.4.10 Epics and Multi-Level Stories
2.5. Project
2.5.1 Scrum Project
2.5.2. Waterfall Project
2.5.2.1 Manage Project Phases
2.5.2.2 Project Design
2.5.2.3 Project Matrix
2.5.2.4 Project Reports and Earned Value Management
2.5.2.5 Project Baselines
2.5.2.6 Project Change
2.5.3. Kanban Project
2.5.3.1 Set Up Kanban Projects
2.5.3.2 Configure Kanban Boards
2.5.3.3 Use Kanban Boards
2.5.4 Hybrid Agile Project
2.5.5 Hybrid Waterfall Project
2.5.6. Project Settings
2.5.6.1 Project Setup
2.5.6.2 Project Executions
2.5.6.3 Project Requirements
2.5.6.4 Project Builds
2.5.6.5 Project Tests
2.5.6.6 Project Docs
2.5.6.7 Project Releases
2.5.6.8 Project Reports
2.5.6.9 Project Risks
2.5.6.10 Project Issues
2.5.6.11 Project Opportunities
2.5.6.12 Project Deliverables
2.5.6.13 Project Reviews
2.5.6.14 Project Process
2.5.6.15 Deliverables
2.5.6.16 Quality Assurance
2.5.6.17 Project-specific Workflow Management
2.5.7 Project Templates
2.6. Execution
2.6.1 Product Planning and Task Breakdown
2.6.2 Task Assignment and Daily Tracking
2.6.3 Build Creation and Test Requests
2.6.4 Bug Confirmation and Resolution
2.6.5 Execution Kanban Boards
2.7. Testing
2.7.1 Write Test Cases
2.7.2 Execute Test Cases
2.7.3 Bug Submission and Reports
2.7.4 Verify and Close Bugs
2.7.5 Test Case Scenes
2.7.6 Submit a Test Request
2.7.7 Test Report
2.8. Agent
2.8.1 Conversation
2.8.2 Sanplex Agents
2.8.3 General Agents
2.8.4 Skill Management
2.8.5 AI Knowledge Library
2.8.6 Models
2.8.7 ZAI Service Installation
2.8.8 ZAI Service Control Panel
2.8.9 ZAI Configuration
2.9. Kanban
2.9.1 Kanban Spaces
2.9.2 Kanban Regions
2.9.3 Kanban Cards
2.10. Company
2.10.1 View Team Members and Work Information
2.10.2 View Recent Company Activity
2.10.3 View and Edit Company Information
2.11. Feedback
2.11.1 Configure, Create, and Review Feedback
2.11.2 Process Feedback and Send Notifications
2.11.3 Tickets
2.12. Admin Settings
2.12.1. System Settings
2.12.1.1 Mode
2.12.1.2 Backup
2.12.1.3 Trash
2.12.1.4 License
2.12.1.5 Security
2.12.1.6 Cron Job
2.12.1.7 Time Zone
2.12.1.8 Rebuild Index
2.12.1.9 LDAP
2.12.1.10 Table Engine
2.12.2 Feature Options
2.12.3. Users Management
2.12.3.1 Set Departments and Edit Company Profile
2.12.3.2 Manage Users
2.12.3.3 Set Permisions
2.12.4. Feature Configuration
2.12.4.1 Dashboard
2.12.4.2 Product
2.12.4.3 Project
2.12.4.4 Execution
2.12.4.5 Test
2.12.4.6 Kanban
2.12.4.7 Feedback
2.12.4.8 Tickets
2.12.4.9 User
2.12.4.10 Relations (Standard Version)
2.12.4.11 Meaturement
2.12.5 Migrate Jira Data to Sanplex
2.12.6 Jira to Sanplex Migration Mapping
2.12.7 Migrate Confluence Data to Sanplex
2.12.8. Agent Configuration
2.13. Asset Library (Premium)
2.13.1 Asset Library Management (Premium)

Manage Stories

2026-08-16 21:06:50
Sanplex Content
775
Last edited by Kelsea Zhang on 2026-10-14 11:39:34
Share links
Summary: Learn how to create and maintain Stories in Sanplex, organize them through Epic, Feature, and Story hierarchies, create items in batches, configure story-related features and permissions, switch list views, link Stories to Plans, and establish relationships through Linked Objects.

Catalog

After Plans are created, product teams can create and maintain Stories in Sanplex. Sanplex organizes story-related work through Epic, Feature, and Story, which can be configured to represent different levels of product stories.

I. Create Stories

1. Create Epics, Features, and Stories

In the current Sanplex interface, story-related work is organized through Epic, Feature, and Story.

Go to the corresponding Epic, Feature, or Story page under Product, and click the Create button in the upper-right corner to create a new item.

The Product Story page in Sanplex, with the Story tab and the Create Story button highlighted.

Sanplex organizes Stories through the Epic, Feature, and Story hierarchy. Parent-child relationships and the built-in SR/sub structure support progressive decomposition, allowing teams to break down higher-level stories into more detailed work items while maintaining clear traceability between them.

2. Split Stories

Stories can be decomposed through the supported story hierarchy.

  • In the Story list, use the available hierarchy or split action to decompose a Story into lower-level items.
  • In the standard Epic–Feature–Story structure, Stories are decomposed level by level rather than directly skipping intermediate levels.
  • Parent-child relationships created through decomposition are displayed hierarchically in the Story list.

The Epic list in Sanplex showing hierarchical story items and hierarchy-related action icons in the Actions column.

After opening a Story, its lower-level items are displayed in the corresponding child-item section, allowing you to review and maintain the story hierarchy.

An Epic details page showing a SubEpic section with nested story items and their available actions.

3. Batch Create

Sanplex supports batch creation for story items. Open the drop-down menu beside Create Epic, Create Feature, or Create Story, and select Batch Create where the option is available.

The Epic list with the Create Epic drop-down menu expanded and Batch Create highlighted.

The Batch Create page provides multiple rows for creating story items together.

The Batch Create page for Epic items, showing multiple input rows and the Bulk upload images and Bulk entry options.

4. Multi-Image Upload

The Batch Create page supports Bulk upload images, allowing multiple images to be added when creating story items in bulk.

The available batch-create fields depend on the current story type and configuration.

5. Multi-Line Entry

Sanplex also supports Bulk entry. Enter one story name per line in the Bulk entry dialog, and the system places the entries into separate rows on the Batch Create page.

The Bulk entry dialog containing multiple story names entered on separate lines.

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.

The Batch Create page showing three story names populated into separate Epic Name rows after Bulk entry.

6. Edit and Maintain Stories

After a Story 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.

The Epic list showing multiple action icons in the Actions column for maintaining story items.

7. Child and Linked-Object Information

Stories 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 Story.

The Epic list showing hierarchical story items and a Linked Objects column containing the number of linked objects for each item.

For parent-child Stories, decomposition follows the configured hierarchy.

  • A parent Story can contain lower-level child Stories.
  • Parent-child relationships are maintained separately from general object-linking relationships.
  • Downstream operations depend on the position of the Story within the hierarchy and the functions available for that story type.

II. Feature and Permission Configuration

1. Story Concept Settings

Administrators can configure the terminology used for the story hierarchy under Admin > Features > Product > Story Concept.

The Story Concept configuration defines the terms used for levels such as Epic, Feature, and Story. Administrators can select an existing concept configuration or use Set Story Concept to maintain the available concepts.

The Admin Features page under Product > Story Concept, showing Story Concept configurations for Epic, Feature, and Story, with options to set, edit, and select the default configuration.

2. Enable Story-Related Product Features

Story-related Product features can be enabled under Admin > Feature Options.

For example, the Product module provides optional features such as Stories and Epics. Select the required options and click Save to make the corresponding features available in the Product module.

The Admin Feature Options page showing the Product module with the Stories and Epics optional features enabled.

3. Permission Settings

Story-related permissions are configured through the system permission groups rather than through separate Epic, Feature, and Story 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 story-related functions.

The Admin Permission page with the Assign Permissions by Modules dialog open, showing Story selected as the module and the corresponding permission sets, methods, and privilege groups.

III. Switch Views

Story-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 story decomposition.
  • A flat list is more convenient when searching, filtering, sorting, or reviewing item attributes independently of the hierarchy.

The Project Story page showing the view toggle buttons for switching between the available list and hierarchy-oriented Story views.

IV. Link Stories to Plans

Plans can be used to organize story-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.

A Plan details page showing the Linked Stories tab with the Stories currently linked to the Plan.

You can also link Stories directly from the Plan List. In the Actions column, click Link Story for the target Plan.

The Product Plan list with the Link Story action highlighted for a Plan.

On the Link Story page, select the Stories you want to associate with the Plan, and then click Link Story.

The Link Story page showing a list of Stories with selection checkboxes and the Link Story button at the bottom.

V. Link Any Story

Parent-child decomposition and general Story relationships serve different purposes in Sanplex.

  • Parent-child relationships represent hierarchical decomposition between story 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 Story 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 Stories or other supported objects even when they do not belong to the same parent-child structure.

A Story details page showing the Linked Objects panel on the right, where related objects can be added and viewed separately from the item's basic information and hierarchy.

Write a Comment
Comment will be posted after it is reviewed.