jira-assistant VS jira

I've been happily using the Jira Assistant browser extension [0] to try to work around the myriad and manifest shortcomings of Jira. It addresses some of them (such as information density on the screen, much more customisable reports).

As others in this thread have alluded to -- corporate security policies can, right or wrong, bring down the banhammer down on these types of tools, which can be doubleplusfrustrating given the native tooling features are so user-hostile.

[0] https://github.com/shridhar-tl/jira-assistant

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