starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 05:46:01 +03:00

[GH-ISSUE #861] feat: 30 day email digest #262

New issue

Closed

opened 2026-02-26 18:46:11 +03:00 by kerem · 8 comments

kerem commented

2026-02-26 18:46:11 +03:00

Owner

Originally created by @anikdhabal on GitHub (Jan 23, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/861

Feature Description

Monthly summary emails for Documenso. Should include the number of documents with different statuses. For example, provide the count of completed documents for the last 30 days.

Use Case

No response

Proposed Solution

No response

Alternatives (optional)

No response

Additional Context

No response

Please check the boxes that apply to this feature request.

I have searched the existing feature requests to make sure this is not a duplicate.
I have provided a detailed description of the requested feature.
I have explained the use case or scenario for this feature.
I have included any relevant technical details or design suggestions.
I understand that this is a suggestion and that there is no guarantee of implementation.
I want to work on creating a PR for this issue if approved

Originally created by @anikdhabal on GitHub (Jan 23, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/861 ### Feature Description Monthly summary emails for Documenso. Should include the number of documents with different statuses. For example, provide the count of completed documents for the last 30 days. ### Use Case _No response_ ### Proposed Solution _No response_ ### Alternatives (optional) _No response_ ### Additional Context _No response_ ### Please check the boxes that apply to this feature request. - [ ] I have searched the existing feature requests to make sure this is not a duplicate. - [ ] I have provided a detailed description of the requested feature. - [ ] I have explained the use case or scenario for this feature. - [ ] I have included any relevant technical details or design suggestions. - [ ] I understand that this is a suggestion and that there is no guarantee of implementation. - [ ] I want to work on creating a PR for this issue if approved

kerem

2026-02-26 18:46:11 +03:00

closed this issue
added the
type: enhancement

apps: web

status: triage
labels

kerem commented

2026-02-26 18:46:12 +03:00

Author

Owner

@anikdhabal commented on GitHub (Jan 23, 2024):

I want to work on creating a PR for this issue if approved.

@anikdhabal commented on GitHub (Jan 23, 2024): I want to work on creating a PR for this issue if approved.

kerem commented

2026-02-26 18:46:12 +03:00

Author

Owner

@dguyen commented on GitHub (Jan 25, 2024):

Could you please outline the use case and proposed solution so we can have a more in-depth understanding of how this will all work?

This sounds similar to #811 where we would display this data on the dashboard, but this PR would be the act of emailing such data monthly?

@dguyen commented on GitHub (Jan 25, 2024): Could you please outline the use case and proposed solution so we can have a more in-depth understanding of how this will all work? This sounds similar to #811 where we would display this data on the dashboard, but this PR would be the act of emailing such data monthly?

kerem commented

2026-02-26 18:46:12 +03:00

Author

Owner

@anikdhabal commented on GitHub (Jan 25, 2024):

Could you please outline the use case and proposed solution so we can have a more in-depth understanding of how this will all work?

This sounds similar to #811 where we would display this data on the dashboard, but this PR would be the act of emailing such data monthly?

We would like to send a monthly email to users, providing a summary of their activity. This summary will include the number of documents that have been completely signed, the count of documents in draft, and the total in pending status over the last 30 days. Additionally, we will highlight the most signed recipients along with their respective numbers in the email.

@anikdhabal commented on GitHub (Jan 25, 2024): > Could you please outline the use case and proposed solution so we can have a more in-depth understanding of how this will all work? > > This sounds similar to #811 where we would display this data on the dashboard, but this PR would be the act of emailing such data monthly? We would like to send a monthly email to users, providing a summary of their activity. This summary will include the number of documents that have been completely signed, the count of documents in draft, and the total in pending status over the last 30 days. Additionally, we will highlight the most signed recipients along with their respective numbers in the email.

kerem commented

2026-02-26 18:46:12 +03:00

Author

Owner

@dguyen commented on GitHub (Jan 25, 2024):

Oh this is for users, from my perspective I don't really see this being used for individual users

This would probably be more relevant for teams or organizations

@dguyen commented on GitHub (Jan 25, 2024): Oh this is for users, from my perspective I don't really see this being used for individual users This would probably be more relevant for teams or organizations

kerem commented

2026-02-26 18:46:12 +03:00

Author

Owner

@anikdhabal commented on GitHub (Jan 25, 2024):

Oh this is for users, from my perspective I don't really see this being used for individual users

This would probably be more relevant for teams or organizations

So, what is your opinion? Should it valid currently, or should we wait further?

@anikdhabal commented on GitHub (Jan 25, 2024): > Oh this is for users, from my perspective I don't really see this being used for individual users > > This would probably be more relevant for teams or organizations So, what is your opinion? Should it valid currently, or should we wait further?

kerem commented

2026-02-26 18:46:12 +03:00

Author

Owner

@dguyen commented on GitHub (Jan 25, 2024):

I think it's currently not relevant at the moment, although in the future it may become applicable

Thanks for bringing this up though, it gives some ideas for much later down the line

I'll close the issue for now

@dguyen commented on GitHub (Jan 25, 2024): I think it's currently not relevant at the moment, although in the future it may become applicable Thanks for bringing this up though, it gives some ideas for much later down the line I'll close the issue for now

kerem commented

2026-02-26 18:46:12 +03:00

Author

Owner

@ElTimuro commented on GitHub (Jan 25, 2024):

@dguyen I Agree, these kinds of update are noise very quickly and need to satisfy a very specific need if done right

@ElTimuro commented on GitHub (Jan 25, 2024): @dguyen I Agree, these kinds of update are noise very quickly and need to satisfy a very specific need if done right

kerem commented

2026-02-26 18:46:12 +03:00

Author

Owner

@anikdhabal commented on GitHub (Jan 25, 2024):

@dguyen @ElTimuro Thanks for your opinion. In the future, I would definitely love to work in this.

@anikdhabal commented on GitHub (Jan 25, 2024): @dguyen @ElTimuro Thanks for your opinion. In the future, I would definitely love to work in this.

kerem referenced this issue

2026-02-26 19:30:40 +03:00

[PR #262] [MERGED] fix: link #833

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#262

No description provided.

Rows
Columns