Live data from Hacker News

GitHub and Jira Software Integration

blog.github.com

21–30 of 222 posts

Re: GitHub and Jira Software Integration

#21

I feel sad for all the Github users who will have to suffer the awful JIRA UX. It’s a tool that tries to be everything to everyone with a decade of legacy cruft attached. The result is something that is slow, confusing, and incoherent. If you have an expert and sink a lot of time into, you can a few decent workflows, but it’s just not worth it. In the end though, don’t worry the managers will get their reports and ev…

Any chance you can suggest a good alternative?

For me its important that it is separate from GitHub for a few reasons:

- having a Jira project means we can easily move issues between projects. This is especially useful for when our support team notices an issue, submits a ticket to our "support ingest" project, and then it can get routed to the correct actual project on the backend. Or when an issue gets misdiagnosed we can move it between projects while keeping a single issue and all the history of it.

- having more complex workflows that allow you to force issues to go through specific steps, trigger webhooks, good fun stuff like that

I really would love a good alternative. Jira has just gotten slower and slower, their UX has gotten worse, and I really would like a good alternative.

However Jira has solid integrations into a lot of places and does a lot of complicated things.

Suggestions?

Re: GitHub and Jira Software Integration

#22
post #5

I know that my experience is by definition limited but across multiple companies & industries the use of JIRA has been uniformly an anti/pattern. GitHub issues on the other hand have never been a negative. The only reason I bring this up is that I think this is an unmitigated bad feature. The only pushback I have at times in an org is the moat between JIRA & Github

Yeah I've had nothing but a bad time with Jira, it's slow / high latency and high impact to use - combining that with GitHubs poor UX and I guess they're made for each other :/

Admittedly I havn't used Jira for about 6 years, but I don't recall it being particularly slow, at least if you give it decent hardware to run on (this is on-prem, so not sure how the Cloud editions go).

If you're talking about process aspects, well.. that's also a business process thing, as to how much information PMs/etc want.

Re: GitHub and Jira Software Integration

#23
post #11

I see a lot of people complaining about JIRA in this thread, so here's my take: - I've used Trello, GitHub Projects/Issues, and other Project Management software; - While JIRA has a steep learning curve and is generally unpleasant to use, it is far and away the most customizable and powerful PM software I have used; - Despite JIRA's poor design choices and UX clunkiness, it is so powerful that I wouldn't use anything…

> "it is far and away the most customizable and powerful PM software I have used"

Opinionated software is good. Unlimited customizability is bad and the source of almost all of Jira's problems.

Re: GitHub and Jira Software Integration

#24
post #7

Jira is the worst bug tracking tool I've ever used.

to be fair, I've never seen a good bug tracking tool

Taiga and GitlabIssues are not too bad. Bugzilla was good 5-10 years ago, now I see it as too complex (and it's written in Perl...).

Re: GitHub and Jira Software Integration

#25

I feel sad for all the Github users who will have to suffer the awful JIRA UX. It’s a tool that tries to be everything to everyone with a decade of legacy cruft attached. The result is something that is slow, confusing, and incoherent. If you have an expert and sink a lot of time into, you can a few decent workflows, but it’s just not worth it. In the end though, don’t worry the managers will get their reports and ev…

Any chance you can suggest a good alternative? For me its important that it is separate from GitHub for a few reasons: - having a Jira project means we can easily move issues between projects. This is especially useful for when our support team notices an issue, submits a ticket to our "support ingest" project, and then it can get routed to the correct actual project on the backend. Or when an issue gets misdiagnosed…

I'd highly recommend Asana. Plenty of integration, performant, and the learning curve isn't too steep.

Re: GitHub and Jira Software Integration

#26
I don't understand the negativity in this thread. Or why people are using this post as an impetus to (ostensibly) move to gitlab. Or lament the decline and fall of github.

Nobody is forcing anyone to use Jira. Nobody is forcing anyone to use Github. You can continue to use both without adopting any of the UX or design or workflows or whatever of the other.

This blog post is just saying "now we have an officially-supported integration that we believe works better than the previous and here are some new features."

Am I missing something here?

Otherwise, congrats to the github team for shipping this! I've used github+jira integrations in the past, and if this is an improvement, then cheers to making things easier for folks who use both tools as part of their day-to-day!

Re: GitHub and Jira Software Integration

#29
post #7

Jira is the worst bug tracking tool I've ever used.

I think it depends on how it's configured and on the team's workflow. It really sucked at my second to last job, but at my most recent job it was reasonably usable, in that about half the time it was better than a comparable tool like Pivotal Tracker or Asana, and about half the time it was worse. A good and bad thing about it is that it isn't a typical single page app - good because it has fewer glitches and bad bec…

You may be right, pivotal might be even worse. Haven't used Asana.
Post reply on HN