Vote #77512
完了Default assigned_to when receiving emails
0%
説明
I have multiple aliases configured to read emails from standard input. For one, I want anything sent to a given alias to be sent to a particular project and assigned to a particular group that's in the project. This is my invocation string (anonymized):
foo: "|cd /path/to/files && /usr/bin/bundle exec rake -f /path/to/files/Rakefile redmine:email:read tracker=Support project=myproject unknown_user=accept no_permission_check=1 assigned_to=MyGroupName status=New allow_override=tracker,status,priority,done_ratio,assigned_to RAILS_ENV=\"production\""
If I just send an email to foo@redmine this doesn't quite work; the issue is created in myproject but the assignee is blank. Now, if I send an email and include @Assigned to: MyGroupName@ it works as expected: the issue is created in my project and is assigned to MyGroupName.
Environment: Redmine version 2.6.8.stable Ruby version 1.8.7-p352 (2011-06-30) [x86_64-linux] Rails version 3.2.22 Environment production Database adapter MySQL
journals
I should have researched this more thoroughly before posting. I realize now that per [[RedmineReceivingEmails]] the only issue options which the rake task will read are @project@, @status@, @tracker@, @category@, and @priority@. It would be helpful to add @assigned_to@ to that list.
--------------------------------------------------------------------------------
Option added in r15547 for 3.3.0.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------