fix: enhance multi-tenant support in notification service (#69)

- Updated tenantId handling in jobData to use params.tenantId if available, falling back to getCurrentTenantId().
- Modified createMilestoneDueNotification method to accept tenantId as a parameter.
- Adjusted processor logic to pass tenantId from job data, ensuring proper multi-tenant functionality.

Author: therealbrad

testplanit/dist/scheduler.js

@@ -11,6 +11,7 @@ interface CreateNotificationParams {
   relatedEntityId?: string;
   relatedEntityType?: string;
   data?: any;
+  tenantId?: string;
 }
 
 export class NotificationService {
@@ -27,7 +28,7 @@ export class NotificationService {
     try {
       const jobData = {
         ...params,
-        tenantId: getCurrentTenantId(),
+        tenantId: params.tenantId ?? getCurrentTenantId(),
       };
 
       const job = await notificationQueue.add(JOB_CREATE_NOTIFICATION, jobData, {
@@ -102,7 +103,8 @@ export class NotificationService {
     dueDate: Date,
     milestoneId: number,
     projectId: number,
-    isOverdue: boolean
+    isOverdue: boolean,
+    tenantId?: string
   ) {
     const title = isOverdue ? "Milestone Overdue" : "Milestone Due Soon";
     const message = isOverdue
@@ -116,6 +118,7 @@ export class NotificationService {
       message,
       relatedEntityId: milestoneId.toString(),
       relatedEntityType: "Milestone",
+      tenantId,
       data: {
         milestoneName,
         projectName,

testplanit/dist/workers/forecastWorker.js

@@ -373,7 +373,8 @@ const processor = async (job: Job) => {
                 dueDate,
                 milestone.id,
                 milestone.project.id,
-                isOverdue
+                isOverdue,
+                job.data.tenantId
               );
               successCount++;
             } catch (error) {