I don't know if there has been conversation about these ideas at all yet but these are two things I would really like to have for the incoming mail module.
1. Some special code developed to indicate tickets to assign incoming mail to --- similar to the {ID####} code that's used for tickets that have email notifications sent already. Often I want to forward some documents into the ticket, it would be easier than downloading them and uploading them to the ticket in this case --- if I could drop a code from the ticket into the subject to re-route that email to the correct ticket this would be ideal.
A work around would be allow some way to force a notification to my own inbox so I can reply to that --- right now I would have to wait for someone else to post a comment before I would have a notification ID to reply to. But if I could force an email of some sort, a summary of the ticket or re-send the last comment as a notification to myself.... this would be a great workaround to me.
2. Ability for html formatting to be parsed and rendered, this might be too much to ask -- but it would be interesting --- whenever signatures contain html in an email then end up clogging up the ticket. Maybe a way to hide certain things would be beneficial when you can't avoid it be sent.
1. You can send email messages to any object that can have comments (tickets, pages, discussions, files...) by including {ID#####} at the end of the email subject line. Note that ID needs to be a real, internal object ID (from project_objects table) - not ticket number. You can see real ID when you hover over Complete link on ticket details page for example.
Please note that this is not "officially supported feature", it's just something that's there and that can be used no matter how inconvenient it can be sometimes to dig for ID-s.
To receive a notification about a specific object, you can always send a reminder to yourself. Reminders also include real object ID in subject and support replies.
2. I doubt that HTML support will happen any time soon.
Thank you for suggestions. If you have further questions, please let us know.
Thanks for the info, even if it's not an officially supported feature --- that works for me. I would love to see something added in the future to show that ID on the Ticket page for example but this works perfectly for me and the internal team -- I wouldn't ask a client to try to understand that of course :)
And I didn't realize I could send a reminder to myself that would contain that, so that works too and would probably be more client friendly if they need the same functionality.
Thanks for creating the Incoming Mail module, we've started using this A LOT --- and things on the dashboard are moving along quite a bit quicker now, no lag in waiting to get time to go to the ticket post the details --- download the files, re-upload them ... etc... just a quick email with the ID number in the subject and all text and attachments are ready and waiting for everyone involved in the ticket.
As for HTML --- I figured :) It was just getting annoying seeing my signature show up as a big mess of html code in the tickets. In most cases I just remove it before sending but sometimes I just bcc in for new tickets when replying to a client.
I just wanted to follow up with you on this, the ID numbers are working great --- we love having this ability. Thank you!
I might need to open a new thread to talk about this idea --- but I'd really love to see some parse tags available in the incoming mail module... I don't know exactly how this would work, maybe there is a standard format somewhere but let's say for example... adding tasks via an email reply.
{add-task:remember to email ilija about email parsing idea}
So if I include something like this in my reply, it will be parsed and added as a task.
I could see a full set of these tags being created and available... maybe simpler than mine... but... covering things like, adding tasks, completing a project, adding and assigning a task. Maybe re-assigning a task that's been assigned to me, etc.
I'm not exactly sure how it would all work but it would be very clever to have some short code for doing at minimum adding a task, and optionally assigning it or dating it. This would be brilliant.
I'd also like to see this on incoming mail for new tickets, you could forward something in and add a list of tasks to be added automatically.
As a side note, because of the "{ID XXXX}" functionality, I am planning to develop a Thunderbird extension that will allow any email to be sent to a ticket, using right-click menus to pull up the tickets by project. Of course, since I've never written a Thunderbird extension before, it may take some time :)
Just to follow up on the parsing idea, I really would love to see this feature --- the more I use the incoming mail module the more I think this would be a huge benefit.
Currently I will forward in new info that I want to track in the tickets and at the top of the email I will indicate some tasks that need to be added because at that moment is the best time to capture those tasks mentally.
I currently do something like this
TASK - Something that needs to get done - 2 days from now
TASK - Something else I need to have a team member do - 2 weeks from now - Assign: Jim
Would be great if we could do something like this easily using formatting and language or pre-determined formatting like standard date format and assignments.
I know I already mentioned it above -- I'm curious if it's in any type of consideration or more of a wishlist status.
1. Some special code developed to indicate tickets to assign incoming mail to --- similar to the {ID####} code that's used for tickets that have email notifications sent already. Often I want to forward some documents into the ticket, it would be easier than downloading them and uploading them to the ticket in this case --- if I could drop a code from the ticket into the subject to re-route that email to the correct ticket this would be ideal.
A work around would be allow some way to force a notification to my own inbox so I can reply to that --- right now I would have to wait for someone else to post a comment before I would have a notification ID to reply to. But if I could force an email of some sort, a summary of the ticket or re-send the last comment as a notification to myself.... this would be a great workaround to me.
2. Ability for html formatting to be parsed and rendered, this might be too much to ask -- but it would be interesting --- whenever signatures contain html in an email then end up clogging up the ticket. Maybe a way to hide certain things would be beneficial when you can't avoid it be sent.
activeCollab +ActiveLabs = Productivity
Quickify, Tabinator Pro, Team Privacy, and more
Consulting + Custom Dev
Free: 7 Tips for activeCollab (PDF)