Check List

Create comment

If task.type equals task send notification text, comment and email accordingly (without smtp)

If task.type equals task send notification text, comment and email accordingly (with smtp)

if task.type equals task send notification text, comment and email accordingly (with custom domain and smtp)

if task.type equals task send notification text, comment and email accordingly (with custom domain smtp and custom email template)

if task.type equals task send notification text, comment and email accordingly (with custom domain smtp and without custom email template)

if task.type equals task send notification text, comment and email accordingly (with custom domain without smtp and without custom email template)

if task.type equals issue send notification text, comment and email accordingly (with custom domain smtp and without custom email template)

if task.type equals issue send notification text, comment and email accordingly (without smtp)

if task.type equals issue send notification text, comment and email accordingly (with smtp)

if task.type equals issue send notification text, comment and email accordingly (with custom domain smtp)

if task.type equals issue send notification text, comment and email accordingly (with custom domain smtp and custom email template)

if task.type equals issue send notification text, comment and email accordingly (with custom domain smtp and without custom email template)

Check if a comment is visible to teammember

Check only can client see his own comment

Check mail body is okay for each type means for task it should mention task and for issue it should mention ticket

Check from mail body redirection link works properly

If client comments in a task/issue, notification, email sends to all superAdmin and manager

if any member comments in a task/issue, notification email sends to superAdmin and manager

UX change comment to client template - > comment on task template

New email template need for comment on Issue

ticket:

⁠

client section e client comment korle (withour order):

⁠

notification: superadmins and company pm mail:

client section e client comment korle (with order): notification: superadmins and pm and mentionsLists mail:

client section e team comment korle (withour order): notification: client mail: client client section e team comment korle (with order): notification: client mail: client

team section e team comment korle (withour order): notfication: super admin, company pm, mention list, assignee team section e team comment korle (with order): notfication: team

task: client section e client comment korle: notification: team (super admin ,admin, manager) client section e team comment korle: notification: client mail: client team section e team comment korle: notification: team

Multi package

CheckList

Local

Test server

Notes

Each service has minimum 1 package

Open

A service can not have more than 3 packages

Open

user can delete a package

Open

user can update an existing package info

Open

After updating existing package, it won’t affect on running order

Open

When a service is delete, all the related packages should delete from DB as well

Open

When creating an order user should able to select package otherwise order won’t create

Open

Create Order from catalog should work perfectly

Open

Create manual order with single service

Open

Create repeated Order with success

Open

User can update the order info with package selection if it’s status===pending

Open

User able to create an add on service successfully

Open

in subscription based service, default duration of a package is month

Open

When user get a service, the package list need to show

Open

When user get a service from catalog, the service page need to show

Open

Successfully fetch service list in catalog page

Open

When user gets all service list, it should show range maximum to minimum range

Open

Check file is properly uploaded in the service

Open

If service is onetime, should not send data of repeatCount, billingCycleCount, repeat duration

Open

if service is subscription should send data of repeatCount, billingcycleCOunt, repeat Duration

Open

A single service can not have multiple packages with same name

Open

While creating a package, at least one feature name should be provided.

Open

A package can have at most 15 features

Open

If at least 1 feature name is not provided during package creation, package won’t create

Open

a package can have multiple feature name

Open

Create service with files

Open

Create service without files

Open

Check without image other file type is denied in service creation

Open

Create proposal with package id successfully

Open

Order Invoice working correctly

Open

Order get works perfectly

Open

Create Order with order form (add on and upsell) works perfectly

Open

Selecting upsell loads the package properly

Open

Order with custom form should be okay

Open

Check stripe payment is working perfectly for both one time and subscription

Open

Check stripe payment is working perfectly for upsell

Open

Check manual payment is working perfectly for both one time and subscription

Open

Check manual payment is working perfectly for upsell

Open

Create task is successful

Open

Task successfully mark as complete

Open

Create service with FaQ

Open

Get service with FAQ

Open

Update service with faq

Open

Create order without projectManger

Open

Create order with project Manger

Open

Create notification while ordering is succesful

Open

Send email to the client after creating an order is succesful (all condition with smtp or without smtp)

Open

CHeck webhook triggered properly while creating order form Manual

Open

Check all the mail works perfectly

Open

if upsell have intake and order form both should take data

Open

taking payment from paypal works (each case)

Open

Invoice send while creating from catalog works

Open

Assume a service is onetime and upsell is onetime too, then multiple invoices send to the clients. means for each upsell and service seperate invoice will be billed

Open

There are no rows in this table

⁠

Files and Folders

CheckList

Local

Test server

Notes

On company create there will be two default folders “All Orders” and “All Tickets”

Open

On workspace create there will be two default folders “All Orders” and “All Tickets”

Open

Folders cannot be created inside of these default folders

Open

Upon company deletion all folders will also be deleted

Open

On order creation, a folder inside “All Orders” with the order id as name will be created by default

Open

On order creation inside the order folder a folder for task file uploads will be created named “Tasks”

Open

Any files uploaded in the order will be shown in the associated order folder

Open

Any files uploaded in the order folder will also be shown in order

Open

Any files uploaded to task will be shown in the “Tasks” folder of the associated order

Open

File can be created inside “Tasks” folder selecting a task

Open

File cannot be uploaded adding deleted tasks

Open

Upon order deletion, all the folders and files inside the order folder will be deleted

Open

if upsell is selected while creating order, separate folder will be created for that

Open

Order folder is also created if proposal is accepted

Open

files attached to proposal will be uploaded to order folder

Open

If files are removed from ticket, then its removed from the folder

Open

Downloading will provide proper download links for all files within the selected folder

Open

When a subscription order is repeated, all the order files and task files will be replicated

Open

Folders with duplicate name is allowed

Open

Folder type === user is required

Open

Invalid folders wont be deleted in folder bulk delete

Open

Files in intake form will also be replicated when an order is recurred

Open

There are no rows in this table

⁠

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.