Issues work fine, but pull requests don't. It should be really easy to add support for these.

Putting this out there in case someone gets to this before me or has comments about the idea...

It would be great to convert an email in gmail to a new trello card, mapping subject to title and ideally with the email content as the initial description.

It would be nice if the bookmarklets only two bits of logic:

1. be able to determine if the current page is a page that it can work on
2. be able to grab pieces of data off of the page

This way the bits which send the data on to cardorizer and the bits that report success or failure back to the user can be shared. The work described in this here might depend on issue #3 which is about getting the bookmarklet code from the server. Once we get that bit done, this unification will make it easy to have one bookmarklet that works on multiple services.

That way I can easily migrate a bunch of these issues on to a trello board. :-)

It looks like this bookmarklet hasn't been touched in a long time. Since then, GitHub now has content security policy set that makes this not work with GitHub.

The jira bookmarklet should escape ampersands and other special characters so they make their way in to cardorizer properly.

This is generally annoying, but causes real problems for some services like Trello because the page very rarely fully reloads. So, you can send one thing over to cardorizer, navigate around and then try and send another thing over, but since the page hasn't reloaded the bookmarklet doesn't work.

I fear that this will require changes to the code in the actual bookmarklet.

It would be nice if the jira bookmarklet created an iframe or something similar that appeared, gave the user feedback, and then disappeared. This way the user would not have to hit back to get back to the screen they were on.

It would be nice if the jira bookmarklet didn't include any logic in the bookmarklet itself other than to get the real logic from the server and call in to it. This will make it simple and safe to make improvements later on without requiring users to update their bookmarklets.