GitHub and Jira Software Integration

Post by ken » Fri, Oct 05, 2018, 2:23 PM UTC

bpchaps wrote: post #40

memset wrote: post #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-supp…

It's because many of us have worked at companies that use JIRA extensively. It's a tool that marks the sign that a company cares more about the management of staff as units, instead of caring about employees as breathing and creative forces. It makes management's job easier, but it does nothing for the managed, except lead to frustration and hundreds of emails that have to be waded through for that 5% chance of relev…

Post by braythwayt » Fri, Oct 05, 2018, 2:28 PM UTC

Spivak wrote: post #188

braythwayt wrote: post #167

Earlier quoted context omitted.

I gently suggest that you examine this thinking, hard. You obviously don’t believe that you have a choice in the matter today. But you also seem to have a helpless belief that you won’t have a choice in the matter tomorrow, nor do you seem to believe there are things you can do to have a choice tomorrow. So instead, you are wishing that something else would force the universe to give you what you want, but without yo…

This is all well and good but I don't think the thinking is wrong, Jira is built and sold to managers who have the authority to impose it on their engineers, (typically dumping a lot of management responsibility onto the engineers in the process but that's a different issue). There's really not much you can do in a lot of orgs except hope that Jira starts to stagnate and rot. So I understand the frustration when some…

Post by ken » Fri, Oct 05, 2018, 2:38 PM UTC

chacham15 wrote: post #65

Karupan wrote: post #39

Earlier quoted context omitted.

For me that’s exactly the problem with JIRA. Each team I’ve worked with uses a different board, workflow, and what not. I still don’t understand the hierarchy. And since it is infinitely configurable, the UX is just horrible. It’s not optimised for any particular audience and is all over the place.

For me this is a huge benefit: the engineering team, product management team, qa team, ux team, etc. can each see the things that are relevant to them in the way that they like while still being able to pass the tasks off to the other teams / track them if they would like. You have to put in work to make each flow work for each customer & make sure that the tags are standardized, but once thats in place its super eas…

Post by [deleted] » Fri, Oct 05, 2018, 3:30 PM UTC

cik wrote: post #186

joeblau wrote: post #164

Earlier quoted context omitted.

There are a lot of engineers on HackerNews who have had terrible experiences with Jira (I'm one of them). You're correct, you don't have to migrate; However, if you work at a company where management all of a sudden realizes — "oh now we can integrate Jira for our tasks". It's a slippery slope down the Jira road. I've had 3 jobs where we used Jira and it was always a nightmare. At Uber ATG it sucked because it was sl…

Somewhere along this thread it became an indictment of Jira. I've spent a tonne of time over the years at multiple orgs both using Jira and trying to move away from it. 10 years later.. I'm back on Jira and won't move. The issues I find (including speed) are really due to the incredibly flexibility of Jira, and things not being thought out by users. Ultimately, I feel like it's akin to the old adage about perl - it d…

Post by techntoke » Fri, Oct 05, 2018, 3:37 PM UTC

braythwayt wrote: post #193

Spivak wrote: post #188

Earlier quoted context omitted.

This is all well and good but I don't think the thinking is wrong, Jira is built and sold to managers who have the authority to impose it on their engineers, (typically dumping a lot of management responsibility onto the engineers in the process but that's a different issue). There's really not much you can do in a lot of orgs except hope that Jira starts to stagnate and rot. So I understand the frustration when some…

Nope, nope, nope. If Jira didn’t exist, someone would build it, because said managers have the budget and authority to spend. If we want a different management culture, we have to work on the culture directly. Which is the entire point of agile, lean, and other movements. As for managers buying it and imposing it on their engineers, we need to recognize that said managers are users too, and their needs matter. It’s n…