I'm interested in some of those personally, have you reported any of the bugs?1. Jira: don't use it, but https://marketplace.atlassian.com/search?query=ticket lists a few that might be adaptable, loads of API eg https://docs.atlassian.com/jira/REST/cloud/#api/2/issue2. SF: don't use it, but they have also have loads of API's, eg: http://developer.force.com/cookbook/recipe/interact-with-the-forcecom-rest-api-from-php3. search: hmm, yes, we need this too. Some of the queries are shocking and literally lock up my db.4. I've heard of the firefox bug.. I honestly didn't believe my user, and he can never replicate it when I'm there, but if you're reporting it too.. hmm. 5. I've only seen the upload error when another javascript error has already been triggered, it's likely something simple, like a missing try/catch, I can never replicate it. (it could even be pjax.. )6. Auto-close: Could be good. Wouldn't take much, we just close everything, if they've more to say, they can reopen.7. Any-Close: Could be good, would take a bit more than #6, (add a form element to the ticket thread, add a backend to the user space code, ensure it's not exploitable)8. Combine/Merge: I think there is a mod for this already.. but it's not integrated. Dunno, haven't used it, we've not needed it.9. Dont-Lock-Notes: Hmm, good point. This should be reported.You've seriously got 10k laying around for this? Wow. To whomever does this, can you hook us up with some/all of your patches for 3 and up?