Yes, it happens with 'bare' backslashes as well. We are on FreeBSD/Postgres8.3 for the backside.

It does seem to be happening on insertion in the database almost. It does NOT double the backslash when previewing...only on save. Sorry! I forgot to mention that...

Not a crucial issue, BTW, just a bit odd...

-Dave

OK, had a question on drawing the 'Milestone' line. It's a bit weird, so I'll add it here as a comment if you really want to accomplish this.

I did this by creating a new card type called 'Milestone'. I parented this card to the main card holding the stories (or tasks) you are SUM ing to cause the burndown.

Add a huge amount of Effort Points to the Milestone card. (I used 100). Set the 'Estimated On' date for the milestone card to the targeted DELIVERY DATE.

I also set a status of "Budgeted" so the Effort points on the milestone would not be included in the SUM of the stories' effort. The MQL table below uses the 'Budgeted' status to exclude the Milestone's Effort.

The line will draw if you add another series to the graph. (see below) It's basically a trend line that trends from 100 to 0 and only draws over 1 data point...vertical.

   
    - label: Milestone
      color: black
      type: hidden
      data: SELECT 'Estimated On', SUM('Effort Points') WHERE 'Status' = 'Budgeted'
      trend: true
      trend-line-color: gray
      trend-line-style: solid
      trend-line-width: 5
      trend-scope: 1
      down-from: SELECT SUM('Effort Points') WHERE  'Estimated On' < '1000-01-1'
    - label: Project Burndown
      color: blue
      type: area
      data: SELECT 'Development Completed On', SUM('Effort Points') WHERE 'Status' = 'Released' 
      trend: true
      trend-ignore: zeroes-at-end
      trend-line-width: 1
      trend-scope: 6
      trend-line-color: black
      down-from: SELECT SUM('Effort Points') WHERE NOT 'Status' = 'Budgeted' AND 'Estimated On' < '2009-02-5'
    - label: Added To Scope
      color: red
      type: area
      trend-line-width: 1
      data: SELECT 'Estimated On', SUM('Effort Points') WHERE  NOT 'Status' = 'Budgeted' AND 'Estimated On' > '2009-02-5'
      trend: true
      trend-ignore: zeroes-at-end
      trend-scope: 12
      trend-line-color: black
      down-from: SELECT SUM('Effort Points') WHERE  'Estimated On' < '1000-01-1'

It seems like this is partly in place. I’ve just noticed that simple value queries can return SOME card properties. Managed Lists do work. Like this:

{{ value query: SELECT ‘Status’
}}

Returns the status of the current card. Other values give no MQL error but are not returned. It would be great if they were.