Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Idea][PAID] Activity Log emails #32

Open
tabacitu opened this issue Oct 16, 2023 · 1 comment
Open

[Idea][PAID] Activity Log emails #32

tabacitu opened this issue Oct 16, 2023 · 1 comment

Comments

@tabacitu
Copy link
Member

I love this package, it does the job very well right now, but it's got one big problem - ME. The things are logged, I should take a look at them weekly but I DON'T.

It would help me a lot to be able to configure when an email that looks like this (I find it most useful by Subject type):

Hi there,

Between X DATE an Y DATE, here's what's happened in your app:

Alternatively, see all activity between X DATE and Y DATE.

I can click on the individual links to go to the List operation filtered specifically for that. Or the bottom link to see all activity.
I think this would cover our use case... and many other use cases.

Would it be difficult to create this? I don't think so. I think it's a quick but efficient thing. But this would be SO HELPFUL to me, that I'm considering we make this a separate package (even PAID). Of course it could also be a FREE package that does NOT depend on backpack/activity-log, but adds those links if it is installed 😔 We could do that too.

What do you think about this @pxpm and @promatik ?

Cheers!

@tabacitu tabacitu changed the title [Feature Request][PAID] Activity Log emails [Idea][PAID] Activity Log emails Oct 16, 2023
@promatik
Copy link
Contributor

I love the idea 👌
I think it should either be;

  1. Free and embedded in the current package.
  2. Paid in a separate package.

So, I just don't like it to be a separate free package 😅

For me, any of those are ok 👌
And I think it would be really easy to do it.

Somethings could go wrong, we would rely a lot on these two;

  • Proper email configuration
  • Proper scheduler configuration

But 1) that's not our job to teach on how to configure it. 2) there are ways to test both and to warn developers if something is not properly working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants