Gojira is the original name of Godzilla and the name of a heavy metal band so I always have to include "github" when I search for it.
Each task is a yaml file and hooked up to your text editor is a language server that can talk to Jira and do autocomplete against @username, Jira ticket ids, etc.
Sync on save.
I’m sure there’ll be all sorts of problems I haven’t forseen, but one can dream of editing task as quickly as editing your personal markdown notes.
As others in this thread have alluded to -- corporate security policies can, right or wrong, bring down the banhammer on these types of tools, which can be doubleplusfrustrating given the native features are so user-hostile.
It was some PTSD inducing work and I couldn't put up with it any longer so I wrote a CLI utility in python where I'd track my work throughout the day, a simple one-liner of the work I did with some hashtags for routing to the right project/client. At the end of the day I would "process" my entries by typing one command which ran chrome+selenium automation to do the work for me.  From memory, API use wasn't allowed which is why I had to take this route - it was also a great conversation starter for anyone passing by while it ran.
I saved a tonne of time and aggravation, others noticed, so I set them up with the same. A nice byproduct of this: all the entries were also kept in a local sqlite database which allowed you to quickly search and find answers for follow-ups without touching JIRA, all with a few characters in the terminal.
Edit: I wanted to say I definitely gained some inspiration by looking at yours.
JiraCLI seems to spend most of its code budget translating in between CLI args and JQL; that's the easy part.
Because every org uses Jira differently, it seems hard to write a generic tool that works well with your org.
My original curl commands: https://gist.github.com/TheMightyLlama/9427202
A TUI always feels like terminal fetishism to me.
So I can do `rm -rf / | jiracli`