Roundup Tracker - Issues


Author rouilj
Recipients rouilj, schlatterbeck
Date 2014-07-21.16:21:25
Message-id <>
In-reply-to Your message of "Mon, 21 Jul 2014 15:36:44 -0000." <> <>
Hi Ralf:

In message <> <
Ralf Schlatterbeck writes:
>On Sun, Jul 20, 2014 at 03:46:37AM +0000, John Rouillard wrote:
>> Maybe as a pre-check before trying to parse the argument list,
>> the code should check to see  if the title (or any prior title)
>> for the issue matches the subject line. If so then it should skip 
>> the argument processing and just add the entry.
>There are already settings for being less strict with suffix parsing,
>Our tracker probably has the default of "strict". I think
>setting this to "loose" will already do what you want?
># Controls the parsing of the [suffix] on subject
># lines in incoming emails. "strict" will return an
># error to the sender if the [suffix] is not recognised.
># "loose" will attempt to parse the [suffix] but just
># pass it through as part of the issue title if not
># recognised. "none" will always pass any [suffix]
># through as part of the issue title.
># Default: strict
>subject_suffix_parsing = strict

Yeah loose gets closer to what I want, but I think I want something
closer to a "recognized" option that passes the []'ed stuff through

  it already has seen it in a title for the issue (ignoring whitespace)

and bounces it if it can't find a title match. That way if an issue
has a title of:

  my title [comment my]

and an email arrives with that subject, the email is accepted. But if
the email arrrives with:

  my title [comment=my_new_comments]

when the field name should be "comments" not "comment", the email gets
bounced since the suffix failed to parse and it is not recognized as a
match for an existing title/subject for that issue.

That being said, should we change the roundup tracker's default to
Date User Action Args
2014-07-21 16:21:25rouiljsetrecipients: + schlatterbeck
2014-07-21 16:21:25rouiljlinkissue2550849 messages
2014-07-21 16:21:25rouiljcreate