ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Multiple email addresses for each user (Feature #461)

Added by Jürgen Hörmann at 2011-06-10 06:47 am. Updated at 2011-12-30 09:52 pm.

Status:Open Start date:2011-06-10
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:Mail Receiving
Target version:-
Remote issue URL: Affected version:

Description

Most of my clients use multiple email addresses to report or answer issues. Mainly because the use a private and business address.
Each time someone uses a new address I need to create a new user and assign this duplicated user to the appropriate project to make the email import work right.

The possibility to assign multiple email addresses to one user would solve this issue and allow my users to use different addresses while import and assignment of emails to tickets would still work as expected.

Associated revisions

Revision bcc90071
Added by Jean-Philippe Lang at 2009-01-25 05:04 pm

Ability to bulk edit custom fields of type 'list' (#461).

git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@2316 e93f8b46-1217-0410-a6f0-8f06a7374b81

Revision cab99aa5
Added by Jean-Philippe Lang at 2010-01-03 12:18 pm

Allow bulk edit custom fields of any type (#461).

git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@3278 e93f8b46-1217-0410-a6f0-8f06a7374b81

History

#1
Updated by Eric Davis at 2011-06-10 04:22 pm

There are two sides to this, how would multiple email addresses work when:

  1. sending an email notification (outgoing email)
  2. receiving an email update (incoming email)

#2
Updated by Holger Just at 2011-06-10 04:28 pm

I guess we should have one primary mail where we send updates to and a couple of secondary ones where we allow incoming issues from and send password-reset mails too.

#3
Updated by Jürgen Hörmann at 2011-06-10 04:42 pm

I like Holgers idea with one addition. Look at this ticket on redmine.org. It would be great if we could set primary and additional email addresses per project.

For me personally ,Holgers suggestion would be sufficient.

@Eric:
Would it be possible to send notifications always to the main address (1) while sending replies to incoming emails always to the last used address (2)?

#4
Updated by Eric Davis at 2011-06-10 04:48 pm

Jürgen Hörmann wrote:

It would be great if we could set primary and additional email addresses per project.

Can you open a new issue for that? It's different enough to track separately.

Jürgen Hörmann wrote:

Would it be possible to send notifications always to the main address (1)

I was thinking the same as Holger but wanted to make sure before I biased anyone:

  • primary email => notifications are sent here only
  • secondary emails => allow receiving email from these

while sending replies to incoming emails always to the last used address (2)?

I have some code that I want to put in 3.0 that might work better. Basically every incoming email gets a confirmation email:

  • "Thank you Jürgen Hörman for your email. An issue update was created at ..."
  • "I'm sorry Jürgen Hörman, the new issue email you sent in was missing the Project and a Due date so it could not be created"

With these confirmations, we could send these back to the actual sender (which could be the secondary). Then they primary email address might also get the Issue update notification.

#5
Updated by Jürgen Hörmann at 2011-12-30 09:52 pm

Hello, I was hoping this feature would get into 3.0.0. I'm sad to see it did not.

This is still my most wanted feature ;) And would make me switch from Redmine to ChiliProject for sure.

Also available in: Atom PDF