znuny / Znuny4OTRS-GIArticleSend

This package enables the standard Generic Interface ticket operations to send articles.
https://www.znuny.com/add-ons/
10 stars 7 forks source link

Email subject format #3

Closed redrick closed 7 years ago

redrick commented 7 years ago

great thing you did here, really appreciate your hard work :)

I got small thing, is not a problem, is more of a feature request...

We use this to send email through API from our employee through OTRS to customer while still keeping copy in OTRS, which is exactly what we wanted, but recently it seems customers are either bothered by the subject line or it gets filtered by their incoming filters as somehow suspicious message....

I had a look and its mainly because subject line contains Ticket ID, which customer does not necessarily need...

I did some digging around and found this: http://lists.otrs.org/pipermail/otrs/2009-November/029266.html

Which is exactly right and can be configured: ticketformat

But that means for us that we change this for the whole system and that would hurt internal process of using OTRS, where we work with this ID to ease the pain of searching and stuff....

Please is there any chance you would consider putting another param in for this?

Ideal case for me is as I added to request these line from this plugin:

ArticleSend => 1,
To          => 'email@example.com', # Email address to send article to.

I would also give it:

SubjectFormat => 'None' # Possible options 'Left', 'Right', 'None'

Otherwise it defaults to system setting described in: http://lists.otrs.org/pipermail/otrs/2009-November/029266.html

Is it anywhere near possible? I am long time Ruby developer with PHP and Python experience, never done fulltime Perl, but I am willing to help if you point me in right direction :)

Thanks a lot :)

thorsteneckel commented 7 years ago

Hi @redrick - Thanks! We're glad you like it. Sadly this sounds like more or less a particular case you are describing. So we currently have no plans to implement this. OTRS will not work properly on responses to that send emails. Since the TicketNumber (identifier) is missing OTRS has no clue that the received email is a follow up and will create a new Ticket - instead of detecting the source ticket and create a follow up for the sending one as it should be. There are some ways to detect this but I'd have to go in to much detail for the scope of this issue. Please make sure this is no issue for your process and remember this change in future issue cases.

However adding this should be fairly easy - especially with the programming background you have 🚀

I added two patches for the current master version: Patches.zip

You will have to apply those changes on any package or framework update. Your package manager will tell you that there are untracked changes. So please be aware.

If you need further support or any other professional enterprise service you can always contact us via support@znuny.com.

Happy hacking!

thorsteneckel commented 7 years ago

PS: If you like to work on a RoR ticketing system we would be happy to have your support over at https://github.com/zammad/zammad 🤓

🚀