go-jira VS jira

In today's article, I would be showing you how to automate Jira with Golang. Jira Software is part of a family of products designed to help teams of all types manage work. Originally, Jira was designed as a bug and issue tracker. But today, Jira has evolved into a powerful work management tool for all kinds of use cases, from requirements and test case management to agile software development. In this article we would be using a go-jira library. To get started, you would need to head over to jira atlas to generate your API token. Ensure to copy your token when you see the copy button after creating as you can't view it afterwards. For the authentication, we would need:

Author of https://github.com/andygrunwald/go-jira here. Let me know if I can help.

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