Feedback
1. Introduction of Sanplex features
1.1. Core Management Framework
1.1.1 Program
1.1.2 Project
1.1.3 Product
1.1.4 Execution
1.1.5 Management Models
1.2. Dashboard
1.2.1 Getting Started with Tutorials
1.2.2 Quick Add
1.2.3 Notification Center
1.2.4 Effort Tracking
1.2.5 Dashboard - Project and Execution
1.2.6 Dashboard - My Work, Contribution, and Recents
1.2.7 Dashboard - Approval
1.2.8 Contacts
1.3. Program
1.3.1 Program List
1.3.2 Program Kanban
1.3.3 Create Program
1.3.4 Create Sub-Programs
1.3.5 Project Charter Management
1.4. Product
1.4.1 Create Product
1.4.2 Manage Modules
1.4.3 Multi-Branch and Multi-Platform Management
1.4.4 Manage Plans
1.4.5 Manage Stories
1.4.6 Requirement Reviews
1.4.7 Requirement Status and Phase
1.4.8 Create Releases
1.4.9 Track Progress
1.4.10 Business Requirements and Multi-Level Requirements
1.5. Project
1.5.1 Scrum Project
1.5.2. Waterfall Project
1.5.2.1 Manage Project Phases
1.5.2.2 Project Design
1.5.2.3 Project Matrix
1.5.2.4 Project Reports and Earned Value Management
1.5.2.5 Project Baselines
1.5.2.6 Project Change
1.5.3. Kanban Project
1.5.3.1 Set Up Kanban Projects
1.5.3.2 Configure Kanban Boards
1.5.3.3 Use Kanban Boards
1.5.4 Hybrid Agile Project
1.5.5 Hybrid Waterfall Project
1.5.6. Project Settings
1.5.6.1 Project Setup
1.5.6.2 Project Executions
1.5.6.3 Project Requirements
1.5.6.4 Project Builds
1.5.6.5 Project Tests
1.5.6.6 Project Docs
1.5.6.7 Project Releases
1.5.6.8 Project Reports
1.5.6.9 Project Risks
1.5.6.10 Project Issues
1.5.6.11 Project Opportunities
1.5.6.12 Project Deliverables
1.5.6.13 Project Reviews
1.5.6.14 Project Process
1.5.6.15 Deliverables
1.5.6.16 Quality Assurance
1.5.6.17 Project-specific Workflow Management
1.5.7 Project Templates
1.6. Execution
1.6.1 Product Planning and Task Breakdown
1.6.2 Task Assignment and Daily Tracking
1.6.3 Build Creation and Test Requests
1.6.4 Bug Confirmation and Resolution
1.6.5 Execution Kanban Boards
1.7. Testing
1.7.1 Write Test Cases
1.7.2 Execute Test Cases
1.7.3 Bug Submission and Reports
1.7.4 Verify and Close Bugs
1.7.5 Test Case Scenes
1.7.6 Submit a Test Request
1.7.7 Test Report
1.8. Agent
1.8.1 Conversation
1.8.2 Sanplex Agents
1.8.3 General Agents
1.8.4 Skill Management
1.8.5 AI Knowledge Library
1.8.6 Models
1.8.7 ZAI Service Installation
1.8.8 ZAI Service Control Panel
1.8.9 ZAI Configuration
1.9. Kanban
1.9.1 Kanban Spaces
1.9.2 Kanban Regions
1.9.3 Kanban Cards
1.10. Company
1.10.1 View Team Members and Work Information
1.10.2 View Recent Company Activity
1.10.3 View and Edit Company Information
1.11. Feedback
1.11.1 Configure, Create, and Review Feedback
1.11.2 Process Feedback and Send Notifications
1.12. Admin Settings
1.12.1. System Settings
1.12.1.1 Mode
1.12.1.2 Backup
1.12.1.3 Trash
1.12.1.4 License
1.12.1.5 Security
1.12.1.6 Cron Job
1.12.1.7 Time Zone
1.12.1.8 Rebuild Index
1.12.1.9 LDAP
1.12.1.10 Table Engine
1.12.2 Feature Options
1.12.3. Users Management
1.12.3.1 Set Departments and Edit Company Profile
1.12.3.2 Manage Users
1.12.3.3 Set Permisions
1.12.4. Feature Configuration
1.12.4.1 Dashboard
1.12.4.2 Product
1.12.4.3 Project
1.12.4.4 Execution
1.12.4.5 Test
1.12.4.6 Kanban
1.12.4.7 Feedback
1.12.4.8 Tickets
1.12.4.9 User
1.12.4.10 Relations (Standard Version)
1.12.4.11 Meaturement
1.12.5 Migrate Jira Data to Sanplex
1.12.6 Jira to Sanplex Migration Mapping
1.12.7. Agent Configuration
1.13. Asset Library (Premium)
1.13.1 Asset Library Management (Premium)

Process Feedback and Send Notifications

2026-10-12 19:06:54
Sanplex Content
7
Last edited by Jing WANG on 2026-10-12 19:30:27
Share links
Summary: Learn how to process feedback by converting it into tickets, stories, features, epics, tasks, bugs, and to-dos, and how to send feedback-related notifications after a release reaches Released status.

Catalog

I. Process Feedback

Submitted feedback can be processed directly from the feedback list. If a Feedback Manager is configured for the product, the feedback workflow can be assigned to the responsible manager.

The Actions column provides processing actions based on the feedback status and available workflow operations.

Feedback list with the Actions column highlighted, showing available processing icons and an expanded action menu.

Open a feedback item to view its description, basic information, processing history, and linked objects. The details page also provides access to information such as Linked Objects, Source, and Internal Contact.

Feedback details page showing the description, Basic information panel, linked work item, processing history, and related object sections.

From the feedback details page, click Convert to convert the feedback into another work item.

Available conversion options include:

  • Ticket
  • Story
  • Feature
  • Epic
  • Task
  • Bug
  • To-do

Convert menu on a feedback details page showing Ticket, Story, Feature, Epic, Task, Bug, and To-do options.

1. Convert Feedback to a Ticket

Select Convert > Ticket to open the ticket creation form.

Sanplex uses available feedback information to prefill relevant ticket fields, such as the product, module, ticket title, and priority. Review the ticket information, complete any required fields, and create the ticket.

Create Ticket dialog opened from feedback, showing product, module, type, assigned user, source, ticket title, priority, description, keywords, and attachments.

After the ticket is created, it appears on the feedback details page as a linked Ticket. The conversion is also recorded in the feedback history.

Feedback details page showing a linked Ticket with its ID, title, priority, and status.

2. Convert Feedback to a Story, Feature, or Epic

Select Convert > Story, Feature, or Epic to create the corresponding work item.

For example, when converting feedback to a Story, Sanplex opens the Create Story page and carries available feedback information into the new item. Review the product, branch and module, hierarchy, reviewer, category, story name, priority, and description before saving.

Create Story page showing product, branch and module, hierarchy, reviewer, category, story name, priority, estimate, and description populated from feedback.

After conversion, the created item is displayed on the feedback details page under the corresponding linked item section.

Feedback details page showing a linked Story with its ID, title, priority, phase, and status.

3. Convert Feedback to a Task

Select Convert > Task from the feedback details page.

Before creating the task, select the Project and Execution where the task will be created, then click Next.

Select Project dialog showing fields for selecting the target project and execution before converting feedback to a task.

On the Create Task page, review the execution, task type, task name, priority, description, and other task information, then click Save.

Create Task page showing the selected execution, task type, task name, priority, estimate, duration, and description.

After the task is created, it appears in the Task section of the feedback details page. The conversion is recorded in the feedback history, and the feedback moves into processing.

Feedback details page showing a linked Task with its ID, title, priority, and status.

4. Convert Feedback to a Bug

Select Convert > Bug to open the Report Bug page.

Review the product, module, affected version, bug name, type, severity, priority, reproduction information, and other available fields before saving the bug.

Report Bug page showing product, module, affected version, bug name, type, severity, priority, and reproduction steps populated from feedback.

After creation, the bug appears in the Bug section of the feedback details page.

Feedback details page showing a linked Bug with its ID, title, priority, and status.

5. Convert Feedback to a To-do

Select Convert > To-do to open the Add To-do dialog.

The feedback title is used as the default to-do title. Configure the date, type, assignee, priority, status, duration, and description as needed, then click Add To-do.

Add To-do dialog showing date, type, assignee, title, priority, description, status, and duration fields.

After creation, the to-do appears in the To-do section of the feedback details page.

Feedback details page showing a linked To-do with its ID, title, priority, and status.

II. Feedback Notifications

Feedback-related notifications can be sent from a release after the associated work has progressed into the release workflow.

When a release is still in Waiting, the Notify action is unavailable.

Project Release page showing a release with Waiting status and the Notify action disabled in the Actions column.

After the release status changes to Released, the Notify action becomes available.

Project Release page showing a release with Released status and the Notify action enabled in the Actions column.

Click Notify to open the Notify Users dialog. Available recipients include:

  • Feedback Provider
  • Product Owner
  • Test Manager
  • Story Creator
  • Execution Team Members
  • Project Team Members
  • Mail to
  • Feedback Manager

Select the required recipients, then click Notify.

Notify Users dialog showing recipient options including Feedback Provider, Product Owner, Test Manager, Story Creator, Execution Team Members, Project Team Members, Mail to, and Feedback Manager.

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