Project

General

Profile

Edit Copy Actions

Feature #9777

open

Subscribers page backend features adding

Added by Divya Inapakurthi 22 days ago. Updated 13 days ago.

Status:
Resolved
Priority:
Normal
Target version:
-
Start date:
07/14/2026
Due date:
07/21/2026 (14 days late)
% Done:

100%

Estimated time:
8:00 h

Description

action history for product subscription,
date range filter for service, product subscribers
sorting for service plans fix
end to end testing service and product subscription


Add

Subtasks 1 (1 open0 closed)

Feature #9798: subscriptions both product and service ResolvedDivya Inapakurthi07/14/202607/21/2026

Delete link to subtaskActions

Add

Related issues

Actions #1

Updated by Divya Inapakurthi 22 days ago

  • Status changed from New to In Progress

Updated by Divya Inapakurthi 22 days ago

Product schema: added stripeCustomerId, stripePriceId, cancellationEmailSentAt; captured at checkout with zero extra Stripe calls.

Removed dead code: the DeliveryJob cancel-cleanup block, which updated zero documents since nothing ever creates a DeliveryJob.

Fixed actor attribution: replaced the broken req.user ? "NurseryUser" : "Client" pattern (always true) with a proper resolveActor(req) based on req.user.role, used consistently across cancel/reactivate/notify/email endpoints.

Filled remaining history gaps: product auto-debit reminder cron; service-side renewal (3 spots in invoicePaid.js) and payment-failure (2 spots in invoicePaymentFailed.js), which had zero history logging before.

New product-subscriber endpoints, mirroring service-subscription capabilities: POST /:id/reactivate (Scenario 1 only — resumes a still-live Stripe subscription; cleanly errors on fully-cancelled ones rather than auto-recreating and charging), POST /:id/send-notification, POST /:id/send-cancellation-email — all admin-only, all writing to history.

Extracted the duplicated cancellation-email logic into a reusable sendProductSubscriptionCancelledEmail in email.service.js

Updated by Divya Inapakurthi 22 days ago

  • Due date changed from 07/13/2026 to 07/14/2026
  • % Done changed from 0 to 60
  • Estimated time set to 8:00 h

sorting by plan titles ranks capitalized and lowercase titles consistently.
Select Scheduled to Cancel in the status dropdown and verify it successfully filters and displays subscribers with status: "scheduled_to_cancel".
Date Filter: Filter by date range (e.g. 07-13-2026 to 07-13-2026) and verify it returns only records created on that day.

Updated by Divya Inapakurthi 21 days ago

Need to test and fix these end to end

subscription-details/ jobs loading issue

customer notification model UI update

subject and tile are same Update regarding your LocalPlan for send notification

update the Reactivate Subscription description with appropriate content

when subscription reactivate or scheduled to cancel, if a job is completed or has any other status, how auto cancelled and new conversion works?

for this subscription SSUB-00215, after reactivation jobs are still has auto cancelled status check and fix for service subscription

for product subscription what will happend to order if a subscription is schedule to cancel and reactivated.

and how orders are created, if multiple orders are pending and payment are done but status or delivery is due for few orders.. how schedule to cancel works. or normally orders are handle.

in product subscribers why not atleast one subscriber even doen't has completed subscription with paymnet and status updated to completed.. why.

Actions #5

Updated by Divya Inapakurthi 21 days ago

  • Status changed from In Progress to Resolved
  • % Done changed from 60 to 100
Actions #6

Updated by Divya Inapakurthi 21 days ago

  • Subtask #9798 added
Edit Copy Actions

Also available in: Atom PDF