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

Feature Request: Email with attachments automated responses from Wekan #3948

Open
xet7 opened this issue Aug 17, 2021 · 9 comments
Open

Feature Request: Email with attachments automated responses from Wekan #3948

xet7 opened this issue Aug 17, 2021 · 9 comments

Comments

@xet7
Copy link
Member

xet7 commented Aug 17, 2021

Originally from Wekan Libera.Chat IRC, moved to there:

From @torwag

Hi, I just started to get intersted in wekan and was wondering most of my "input" to wekan would be from emails (we are still for communication a very much email based organisation). So I am looking for ways how to get the content of an email (with attachements) into wekan most effeciently and easily. If possible I also want to automate the process of answering resp. sending emails based on the state in wekan. Is there anything like this?

From @pitastrudl

#794 seems to be an issue open for this, hope you find your answers here

From @xet7

I think it's some of these:

  • Email to board. It is waiting for mass transfer to be implemented first.
  • Currently I'm in progress of trying to fix email sending Test all email SMTP settings, which ones work #3702. I kind of promised to one of my clients, that I'll try to get it working this week. Sending with AWS SES works, but I'll try to get sending with O365 etc working.
  • There already is some IFTTT Rules for sending email, if it does not have enough features, it could be improved.
  • There is some scheduler code https://github.com/wekan/wekan-scheduler although I don't know is it related. Anyway, point is to integrate those external scripts directly into Wekan sometime.
@sebnem-an
Copy link

sebnem-an commented Mar 9, 2022

Dear community, I would like to ask whether the feature "Send email to wekan board and automatically creation of card" has already been implemented? Thank you very much! @xet7

@xet7
Copy link
Member Author

xet7 commented Mar 9, 2022

@schulz

You wrote at #2870 (comment) that you have some more features you have not sent as pull request to WeKan yet, like:

Do you have time to send those?

@sebnem-an

Currently there is only:

TODO:

@schulz
Copy link
Contributor

schulz commented Mar 28, 2022

@xet7 I'm in Ukraine and we're fighting with Russia here but will look into it once it's all comes to an end.

@sebnem-an
Copy link

So sad about that! 😭😭😭

@webenefits
Copy link

Hey @xet7
would this issue be solved faster with a donation (maybe in a time frame of 4 to 6 weeks) or only if we work out a solution ourselves and create a pull request?

@xet7
Copy link
Member Author

xet7 commented Feb 15, 2023

@webenefits

Only if you work out a solution yourselves and create a pull request.

My next 6 weeks goes to features/fixes for one customer, and after that to other customers.

Node.js 14 EOL is in 2 months and 2 weeks, 30 Apr 2023. Upcoming Meteor 3.0 will have Node.js 18 support and migration guides for code changes required, those could take a lot of time, to keep Meteor WeKan working. Meteor uses newest MongoDB. Newest Node.js MongoDB drivers have some new deprecations etc so Meteor devs need to make some changes to keep MongoDB working properly with Meteor.

I'm not yet sure can all paid features be implemented in Meteor WeKan, or will they be tested first in some Multiverse prototype. Anyway I try to find a way to keep all features in all versions of WeKan.

@webenefits
Copy link

Thank you for your quick feedback. We will try to create a pull request if we have time.

@webenefits
Copy link

Hi @xet7 why is this feature request closed? Has it been solved?

@xet7 xet7 reopened this Feb 13, 2024
@xet7
Copy link
Member Author

xet7 commented Feb 13, 2024

@webenefits

I don't remember why this was closed, maybe it was some mistake. This feature is not yet in WeKan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants