allow_override does not work as expected

Added by Gerhard Gappmeier almost 7 years ago

I'm using the email Gateway using the script /usr/bin/rake redmine:email:helpdesk:read
as explained here:
http://www.redmine.org/projects/redmine/wiki/RedmineReceivingEmails#Issue-attributes

The exact command called from my procmail filter looks as follows:

* ? sudo -u www-data /usr/bin/rake redmine:email:helpdesk:read RAILS_ENV="production" project=helpdesk tracker=support allow_override=project,severity,compiler,operating\ system,affected\ version,customerid

Some of these fields are custom fields, but according to the doc this should work.

The mail body (Generated by a web form) then contains the following keywords.

customerid: 001462
project: project-id
severity: Normal
affected version: 1.1.0-158
compiler: gcc
operating system: Linux Yocto
platform: ARM Linux
product: productname

more text

The ticket gets created, but the allow_override does not work as expected.
In Redmine the resulting text looks as follows:

customerid: 001462

severity: Normal
affected version: 1.1.0-158
compiler: gcc
operating system: Linux Yocto
platform: ARM Linux
product: productname

more text

The only field that worked was 'project', so this disappeared from the text.
All other fields are not evaluated and remain in the text.

Does anybody know what the reason for this can be?

Replies (2)

RE: allow_override does not work as expected - Added by Bernhard Rohloff almost 7 years ago

Does it work if you replace your attributes for the allow_override option with all?

RE: allow_override does not work as expected - Added by Gerhard Gappmeier almost 7 years ago

all is not what I want, but I tried it to see if it makes a difference.
Actually it didn't work at all. Even project didn't worked anymore,
so the ticket got assigned to the defaut project=helpdesk, instead of the one specified in the mail body.

more info: the docs state the the fields on the command line must be lower case.
In the mail body I tried both, lower case keywords and exact camel cased like the fields are defined
by redmine and in my custom field table.
both times with the same results.

Is there any trace I could enable to track down the reason why it is getting ignored.

BTW, here is my redmine version info:

Environment:
  Redmine version                3.3.1.stable
  Ruby version                   2.3.3-p222 (2016-11-21) [x86_64-linux-gnu]
  Rails version                  4.2.7.1
  Environment                    production
  Database adapter               Mysql2
SCM:
  Git                            2.11.0
  Filesystem                     
Redmine plugins:
  redmine_agile                  1.4.2
  redmine_checklists             3.1.5
  redmine_contacts               4.0.5
  redmine_contacts_helpdesk      3.0.5
  redmine_contacts_invoices      4.1.3
  redmine_favorite_projects      2.0.3
  redmine_finance                2.1.1
  redmine_my_page                0.1.10
  redmine_products               2.0.1
  redmine_questions              0.0.7
  redmine_workflow_enhancements  0.5.0

(1-2/2)

Project

General

Profile

Redmine