Changing email notifications to come from user not AC

avatar glawrie Pro Jun 16. 2009. 8:31 pm #1
All the notifications sent by AC are shown as coming from the 'Notifications From' id stated in Admin / Mailing options.

Is there a way to change this so that some notifications (for example of comments to messages) come from the user making the update? Or perhaps this is coming in a later update? I think this (or the option of this) would be more useful than all notifications coming from the system
avatar Ilija Studen Staff Jun 16. 2009. 9:05 pm #2
There is currently no way to make the notifications have From set to a specific user and we do not have plans to introduce than in the near future.
Follow @activecollab and activeCollab on Facebook.
avatar glawrie Pro Jun 16. 2009. 9:11 pm #3
OK - pity.

Presumably it is not that hard to do - as AC knows who just added the comment, and presumably the 'name field' in the outbound email is pulled from a field (e.g. you could simply change the displayed name in outbound email, leaving the email address as one stated in the Mailing setup).

WRT to future developments - is there a roadmap outlining what is likely in future versions available? Would be helpful.
avatar Ilija Studen Staff Jun 16. 2009. 9:14 pm #4
glawrie:
WRT to future developments - is there a roadmap outlining what is likely in future versions available? Would be helpful.


While there is a brief roadmap (one, max two releases ahead), it's for internal use only.

We do not publicly discuss features until we have shippable code, at least for limited group of beta testers. Actual, working code is much more valuable than any discussion about particular feature.
Follow @activecollab and activeCollab on Facebook.
avatar glawrie Pro Jun 16. 2009. 9:38 pm #5
Well each to their own I guess. I don't agree that a 'surprised' customer is necessarily a happy one.

We're currently spending a bit of money adding a feature that is missing, and from reading this and other bits of the forum plenty of people are struggling to work out how to patch up the code from approximately zero documentation. All this is pretty inefficient if you are working to introduce similar features concurrently.

To be candid, I am not sure I understand your final comment above: of course working code is valuable, but baffled why discussing your plans for the product is counterproductive. You worried 37 Signals might rip off your ideas...? (oh - maybe so - that's how AC got started after all isn't it... I seem to recall brave talk of creating an open source version of Basecamp in the early days).
avatar Ilija Studen Staff Jun 17. 2009. 10:49 am #6
Reason why we don't discuss features that are not yet part of the product is explained in comment #6 of discussion I linked in previous message. Decision to go without public roadmap is not influenced by secrecy or fear that someone will steal our ideas. Quite the contrary, ideas are a dozen a dime and all you need to do to get a bunch of great ones is to read through feature requests forums or google a bit.

Everything boils down to philosophy that we are in business of selling working software, not ideas or stuff that exists only in our heads. When we get to shippable code, than we'll discuss it, but not before.

If you would like to continue this discussion, please do that in appropriate topic.
Follow @activecollab and activeCollab on Facebook.