Possible bug in subject line parsing for ticket #'s?
Due to a transition issue hitting us when moving to an old ticketing system to SD+, we're having to open tickets in the old system, but include information for reference in SD+.
This ends up creating subject lines that look like this:
##1234## - 45678 Issue with software FOO
This is forwarded or replied to from within SD+, and our incoming mailbox is included in the list of addresses to receive this.
It ends up coming into the incoming mailbox and creates a NEW ticket (not 1234). This leads me to believe that there is a "greedy parsing problem" with SD+.
In other words, I believe the ## is looked for, then greedily searches for numbers, but goes to the end of the line, working its way backwards, finds 45678, then starts searching for a closing ## notation, and finding none, creates a new ticket.
(I know I'm delving into black art mysteries of parsing, but having gotten quite good at Perl and the intricacies of deep parsing, I know from whence I speak! :-)
Besides, having sat at the feet of Jeffry Friedl gives me an honorary scholarship.)
So, do we have a bug?
Justin
This ends up creating subject lines that look like this:
##1234## - 45678 Issue with software FOO
This is forwarded or replied to from within SD+, and our incoming mailbox is included in the list of addresses to receive this.
It ends up coming into the incoming mailbox and creates a NEW ticket (not 1234). This leads me to believe that there is a "greedy parsing problem" with SD+.
In other words, I believe the ## is looked for, then greedily searches for numbers, but goes to the end of the line, working its way backwards, finds 45678, then starts searching for a closing ## notation, and finding none, creates a new ticket.
(I know I'm delving into black art mysteries of parsing, but having gotten quite good at Perl and the intricacies of deep parsing, I know from whence I speak! :-)
Besides, having sat at the feet of Jeffry Friedl gives me an honorary scholarship.)
So, do we have a bug?
Justin
