Feature versioning Enhancements

icon picker
Feature Version Table (Changelog)

Feature version
Feature name
Feature Version
Version
change description
Notes
Status
Release on
Dependency
Conflict Risk
Priority
Service
Open
One time service
Open
Subscription service
Open
Multi Package
Open
Proposal
Open
Invoice
Open
Add on
Open
Coupon
Open
Forms
Open
Workspace
Open
There are no rows in this table
Change Log
Date
Version
Change Type
Description
Impact
Reason for Change
Author/Developer
Status
3/3/2025
v1.8.5.3
For rectangular logos: make it default is user has given rectangular logo
SuperAdmin, Admin, Client, PM, Assignee
PM
3/4/2025
vX.X.X
appsumo package custom email no has been updated.
appSumo User
Dev Team Name
3/4/2025
vX.X.X
User no will be per workspace.
User
Dev Team Name
3/10/2025
vX.X.X
email field is non editable for convert to client
Client, Superadmin,Admin
UI Team
3/11/2025
vX.X.X
Client email can be updated
SuperAdmin, Admin,client
Product
3/12/2025
vX.X.X
100% coupon is not applicable for paypal
Admin. client
Product
3/17/2025
firstname will require atlest 1 character for client/leads
client, lead
Product
3/21/2025
SuperAdmin/admin can create service with 0$ (currency)
One time service, Order page, invoice
CTO
3/27/2025
Adding “Send invoice” button directly while creating send invoice
Invoice, Client
PM
4/17/2025
Leads number update to 50000 in enterprise plan
4/24/2025
In manual invoice once a service is selected show setup fee. and setup fee should be editable
Invoice,
4/25/2025
Client field is editable
client, sign in url
4/28/2025
email template can be edited without setting up email address
email
4/28/2025
Keep the acess for 10 more days if subscription fails
Link to doc:
There are no rows in this table

Guidelines for Coda:

Date: Use the date format YYYY-MM-DD (e.g., 2025-03-15).
Version: Follow semantic versioning (e.g., v2.0.0, v2.0.1).
Change Type: Select from predefined tags (New Feature, Enhancement, Bug Fix, UI/UX Update, Security Update, Deprecated, feature update).
Description: Keep it concise but informative.
Impact: Identify affected users or system components.
Reason for Change: State the rationale (e.g., User Feedback, Bug Resolution, Security Enhancement).
Author/Developer: Record the responsible team or individual.
Status: Use standardized status tags (Planned, In Progress, Testing, Released, Rollback).

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.