id,summary,reporter,owner,description,type,status,priority,component,severity,resolution,keywords,cc,release
7559,SQL query messed up,dnedelchev,rjollos,If you write the following in a wiki page:\r\n\r\n{{{\r\nsee #1 and #2 and #3_ probably #4; maybe #5- and #6\r\n#7:eventually\r\nticket:8_ ticket:9 and [ticket:10] ?\r\n}}}\r\nthen only tickets 2 and 10 would be detected by the macro.\r\nThe reason is the quiery is only for tickets referred in the following form:\r\n * {{{'#3 '}}} (i.e. a trailing space is mandatory!) \r\n * {{{'[ticket:3]'}}} (i.e. a trailing space is mandatory!)\r\nIf the trailing space as well as enveloping brackets are just removed_ all tickets except ticket 1 are detected. But then references like these:\r\n * {{{other_trac:#3}}}\r\n * {{{other_trac:ticket:3}}}\r\nwill also be detected while they obviously shouldn't be.[[BR]]\r\n(I didn't investigated yet why ticket 1 is handled different - in some cases it's missed when other tickets referenced in the same form are detected normally)[[BR]]\r\n\r\nIn short: I think the SQL query have to be rewritten from the beginning since I think it should be made much more clean.[[BR]]\r\nI'll try to un-ravel it a bit more if I have time but I'm not too much in that matter and I'm sure someone else can do it much better than me.\r\n\r\n(see also #7299),defect,assigned,high,BackLinksMacro,normal,,,,0.12