Feature #3706
Allow assigned_to field configuration on Issue creation by email
| Status: | Closed | Start date: | 2009-08-03 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Eric Davis | % Done: | 100% | |
| Category: | Email receiving | |||
| Target version: | 1.0.0 (RC) | |||
| Resolution: | Fixed |
Description
- project=PROJECT identifier of the target project
- tracker=TRACKER name of the target tracker
- category=CATEGORY name of the target category
- priority=PRIORITY name of the target priority
Is it possible to control the assigned_to field too? I'm already using Redmine to control a distributed development process (about a hundred users) and at this moment we need a way to register (as a Redmine issue) all the support e-mails we are receiving from external users. All these emails must be assigned to a specific Redmine user for helping our user support process.
I'm testing the trunk version (rev 2835) which already include the great job described in http://www.redmine.org/projects/redmine/repository/revisions/2789.
Related issues
History
#1 Updated by Mischa The Evil almost 4 years ago
- Tracker changed from Patch to Feature
#2 Updated by Marcin Trendota almost 4 years ago
Vote for it ;)
I would do it by myself if only i knew ruby (or have time to learn it)...
#3 Updated by Jean-Philippe Lang over 3 years ago
- Category changed from Email notifications to Email receiving
#4 Updated by Emils Klotins over 3 years ago
Marcin Trendota wrote:
Vote for it ;)
I would do it by myself if only i knew ruby (or have time to learn it)...
Likewise, it would so much help setting up automated issue entry in some cases.
#5 Updated by Erica Gallindo over 3 years ago
When I first suggest this, I wasn't aware how to use categories for this purpose. Now, I know it's possible to control the assigned_to field using categories. When a category is created it is possible to configure a redmine user for that. Thus, simply chosing a category for an issue when its is created will automatically fill the issue "assigned_to" field with category configured user.
#6 Updated by Enderson Maia about 3 years ago
+1
I suggest that the CC: field could be used as a assigned_to: , and CC: just for watchers.
So a message with:
.. to: <redmine@example.com>, <user@example.com> cc: <somebody@example.com>, <someone@example.com> ...
would be created a issue assigned_to: <user@example.com> and <somebody@example.com>, <someone@example.com> for watchers.
In this case using <redmine@example.com> as the incoming e-mail, I just don't know how Redmine could make this distinction.
Another option would be to make allow-override accept the assigned_to: as an option, and the assigner users could be set on the e-mail body.
#7 Updated by Eric Davis about 3 years ago
- Status changed from New to Closed
- Assignee set to Eric Davis
- Target version set to 1.0.0 (RC)
- % Done changed from 0 to 100
- Resolution set to Fixed
Added support for setting an issue's assigned to field via email. It will take a user's email address, login, or full name. r3764