Aye Aye Aung #84
openPricing Package Core Management
100%
Description
Implement CRUD operations for pricing packages.
Develop functionality to define and manage key features for each package (e.g., Free, Standard, Premium).
Set and manage pricing for each package, including associated features.
Updated by Aye Aye Aung 11 months ago
- Due date set to 02/07/2025
- Assignee set to Win Lae
- Priority changed from Low Priority to Normal Priority
pricing_packages_tbl
id (BIGINT UNSIGNED)
name (VARCHAR(255))
description (TEXT)
price (BIGINT)
created_at (TIMESTAMP)
updated_at (TIMESTAMP)
Updated by Aye Aye Aung 11 months ago
Here is the sample package.
Package 1: Free
Name: Free
Description: A basic, no-cost package suitable for smaller-scale or trial use.
Price: 0 MMK
Created_at: NOW()
Updated_at: NOW()
Package 2: Standard
Name: Standard
Description: Standard package with medium features. Best for moderate usage.
Price: 1999 MMK
Created_at: NOW()
Updated_at: NOW()
Package 3: Premium
Name: Premium
Description: Premium package with full features. Ideal for large scale use.
Price: 4999 MMK
Created_at: NOW()
Updated_at: NOW()
Updated by Aung Phyo Oo 11 months ago ยท Edited
- Due date changed from 02/07/2025 to 02/14/2025
- Status changed from Resolved to Reopened
Updated by Aung Phyo Oo 11 months ago
- Due date changed from 02/14/2025 to 02/07/2025
- Status changed from Reopened to Resolved
Updated by Aye Aye Aung 9 months ago
We need to add following database field and modified CRUD
pricing_packages_tbl
id (BIGINT UNSIGNED)
name (VARCHAR(255))
description (TEXT)
voter_limit (INT) - Max number of voters allowed
features(json) - List of features included in JSON format
price (BIGINT)
is_active(Boolean) - Whether the package is currently offered
created_at (TIMESTAMP)
updated_at (TIMESTAMP)
Updated by Aye Aye Aung 9 months ago
- Due date changed from 02/07/2025 to 04/25/2025
- Status changed from Resolved to Reopened
- Start date changed from 01/07/2025 to 04/24/2025