jira VS finstem

It seems that Jira is so unbearably universally slow that lots of people tries to interact with it via some custom made tool.

A friend of mine told that one of his jobs he developed simple internal Qt client to perform basic tasks in Jira.

And when I was required to track my tasks in Jira I created a bunch of custom console scripts make all changes via https://github.com/go-jira/jira .

I use GoJira for this (https://github.com/go-jira/jira) and I'm mostly happy with it.

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.

I had used https://github.com/go-jira/jira in my previous job. custom-commands is very useful feature. I had built a set of commands to filter out issues for different use cases. The command line approach was way faster than waiting for the jira page to load and click the correct set of filters.

Don’t waste time on it. Instead, start using gojira which is a jira tui made in go. You’ll thank me later.

I use https://github.com/go-jira/jira a lot for generating reports. Have you compared the features of it to the cli you're making?

I feel enslaved by JIRA. I hated it for a long time. Now I feel beaten into submission. There has got to be another way, but I've yet to see it. For a while I was trying to use the go-jira command line tool to help easy the pain, but it's buggy and frustrating which is kind of expected given that it's not maintained by Atlassian.

It's funny because I have never seen the mentioned Firefox error on any Jira instance. The problem is mostly server-side: it's slow as hell! I'm personally using go-jira [0], but even that is slow: the problem as I said is not (only) the frontend, but the backend.

[0]: https://github.com/go-jira/jira

It ain't much, but it's honest work: https://github.com/hiAndrewQuinn/finstem

I moved to Finland a few years ago to be with my then-fiancee, now-wife. I started learning Finnish and found that constantly going to Wiktionary to search for the root forms of their words, which have 15 declensions, possessive endings, clitics similar to Japanese particles, and other craziness going on in the root form themselves.

I wrote this to let me very quickly strip away all of that and get just the original dictionary forms of words. Later I wrapped it into a little `fzf` script to make it easy to analyze entire sentences or paragraphs at once.

The code is nothing special at all, but I use this thing dozens of times daily, and it's never let me down.

I know it goes without saying for most of us here, but actually being a heavy terminal user yourself is one of the most important things to understand how to design CLIs. It helps a ton to understand the ecosystem you live in, not just your own organism.

Example: Something I did a few months back ago for a tiny personal project @ https://github.com/hiAndrewQuinn/finstem was implement `--format CSV`, `TSV` and `JSON` flags. I haven't had need for any of these myself, but they exist so any future people who want to use `csvkit`, `awk` and `jq` respectively to wrap around my program have easy ways to do so. That's not stuff I would have had the instincts to do if I wasn't myself a user of all 3 of those programs.

Most of the software I write is at least somewhat cold-blooded by this definition. My program to find the dictionary forms of Finnish words is an okay example:

https://github.com/hiAndrewQuinn/finstem

I wrote the initial draft in an afternoon almost a year ago, and from then on endeavored to only make changes which I know play nicely with my local software ecology. I usually have `fzf` installed, so an interactive mode comes as a shell script. I usually have `csvkit`, `jq`, and if all else fails `awk` installed, so my last major update was to include flags for CSV, JSON, and TSV output respectively. Etc, etc.

The build instructions intentionally eschew anything like Poetry and just gives you the shell commands I would run on a fresh Ubuntu VirtualBox VM. I hand test it every couple of months in this environment. If the need to Dockerize it ever arose I'm sure it would be straightforward, in part because the shell commands themselves are straightforward.

I'm considering taking a tool I have which has a pretty nicely fleshed-out CLI interface and wrapping a GUI around it, so people who don't run desktop Linux can use it too. This seems like it might be perfect for my needs.

https://github.com/hiAndrewQuinn/finstem

Big GitHub link

I build little CLI tools in Python non-stop. ChatGPT and some basic knowledge of how the `click` library works has made it almost completely trivial to get the ball rolling for whatever need I have for it, `--help` text included.

The fact that the barrier for creation is so low means I'm even willing to do them to solve very niche problems in generalizable ways. [1] is common enough that a few people have starred it. [2] is niche enough that other Anki folks haven't used it AFAICT. [3] is likely something I'll never personally need again, even though Azure VM reservations not letting you customize your reminders for when they're about to expire is probably a costly mistake for a great many firms. All generated with this same starting methodology, because what I wanted was just a little too fiddly to want to hack together with my shell toolkit.

[1]: https://github.com/hiAndrewQuinn/finstem

[2]: https://github.com/hiAndrewQuinn/table2anki

[3]: https://github.com/hiAndrewQuinn/AzureReservations2ICS