plugin uses humongous javascript ajax thing

[anonymous]

Why why on earth, include this horrible jquery.js client side hackery when you have python on the server?

this plugin just does not work unless you allow this javascript cr*p to run, so out it goes.

[Noah Kantrowitz]

1. This plugin will "work" without JavaScript, you just won't get clickable links for the ticket numbers in the Blocking/Blocked By fields. You also won't see the "resolve as" option disabled, though trying to use it for a blocked ticket still won't work (it double checks server-side).
2. This is needed because the way the templates are setup, if I put markup as the value of a field, it also gets added as the value attribute of the entry box at the bottom of the ticket form. This results in HTML that looks like this:

   <input type="text" name="blocking" value="<a href="/ticket/1">#1</a>" />
   

which is clearly invalid. There is no way in these templates to tell it to escape in one place but not another. Similarly there is no way in the template to disable an action, so this has to be done client-side.