Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub and Jira Software Integration

blog.github.com

Post reply on HN
Print view View original

181–190 of 222 posts

Re: GitHub and Jira Software Integration

#181

Post by lmm »

ahi wrote: post #52
bpchaps wrote: post #40

Earlier quoted context omitted.

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…

I work in a shop that had effectively no project management. When jira was introduced it was a godsend. Obviously email and slack requests aren't better, so what is the alternative system that has people hating on jira? Honest question.

Trello. No "workflows" that force you to drag the ticket through 5 different columns to get it to the state you wanted (or, even better, just make it completely impossible to undo a mistake), no approvals, no waiting 5 seconds for the UI every time you change something, just a bunch of task cards in columns that you drag between them.

Re: GitHub and Jira Software Integration

#182

Post by lmm »

sneak wrote: post #153
hardwaregeek wrote: post #41

Earlier quoted context omitted.

> Nobody is forcing anyone to use Jira. Nobody is forcing anyone to use Github. I agree that the negativity doesn't seem warranted, but plenty of people are being forced to use Jira or GitHub in their daily routines.

That’s not what “forced” means. There are plenty of other jobs, especially for the kinds of people who find Jira in their workflows.

If you know a company that's hiring and has "no Jira" written into the contract, please let me know where! It's easy to find a job at a company that isn't using Jira right now, but then a tool like GitHub offers an integration and they change their minds.

Re: GitHub and Jira Software Integration

#183

Post by lmm »

tootie wrote: post #14

JIRA is the top project management platform for good reason. I know a lot of people complain that it's complicated, but every time I've something simpler we end up hitting a wall. JIRA just needs a sensible workflow configured for your project and it's great. All that being said, I don't get this move. Atlassian has a very capable git product. GitHub should have attempted to anoint a new tool.

> JIRA is the top project management platform for good reason.

As others have said, it's popular with managers, not with developers, but managers make these decisions. I've worked at several places that used JIRA and it was always hated by rank-and-file developers but imposed from above.

Re: GitHub and Jira Software Integration

#184

Post by lmm »

kuyan wrote: post #56

My office usees Jira. I like it. I feel that a lot of the sentiment against Jira is a result of bad management - Jira is a tool. It can be used by good managers, and it can be used by bad managers.

Tools drive the way they're used. You have to go out of your way to use Jira well, the path of least resistance is to use it badly (e.g. task state transitions default to disallowed and you have to explicitly allow the ones you want to permit, so your workflow will be too restrictive unless you've gone out of your way to fix it).

Re: GitHub and Jira Software Integration

#185

Post by wonderwonder »

closeparen wrote: post #140
chii wrote: post #92

Earlier quoted context omitted.

all of those problems you have aren't inherently a problem with the Jira product. They are organizational problems, management problems, and communication problems. If you have any of those problems, replacing Jira with another issue tracker will not solve it. Jira gets the flac, because but the problems isn't Jira.

JIRA makes it dangerously easy to implement overly bureaucratic processes. A certain kind of organization is drawn to it for that reason. Even a healthy organization switching to JIRA can get carried away with the tools now at its disposal. JIRA is a software product but also a social institution, an organizational philosophy. Sure, you can have the software without the attitude or vice versa, but use of JIRA is stil…

So your argument is that JIRA is too good and gives the user too much freedom to do what they want? Software is a tool, it is there to do what the user wants, a good tool does not limit the user. Organizational processes are just that, those selected by the org.

JIRA is successful because it is a good tool that gives power to the users. Anyone is free to build a competitor to JIRA, but I would argue that if the developer limits it and forces the client to use their preferred process methodology that they will likely fail.

Just my opinion. I have only been using JIRA for a few weeks now, have had no issues. Nothing amazing about it and nothing terrible. It does the job. Its just a tool. How its used is up to the user.

Re: GitHub and Jira Software Integration

#186

Post by cik »

joeblau wrote: post #164
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…

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 does everything including giving you the rope to hang yourself.. it's up to you if you hang yourself. That plus all my friends who insist one needs a PhD in Jira, to Jira... but I digress.

We're set up appropriately with issue types, differentiation between issues, bugs, tasks, (and our version of etc). We can plan sprints locally and remotely, and have all our dashboards and friends immediately update. Integrated (sanely) with confluence we get retrospectives, historic reports. We create bugs, move their states, deal with Agile and Kanban, have histories... the whole deal. To reduce the inherent pain in dealing with bug creation because it generally sucks, we have a slack integration I wrote to: a. Create a bug b. When you type ISSUE-ISSUE# into a channel, the robot picks up and gives us all the subject.

The combination above removed all friction. The one thing I wish would happen from a workload perspective is that when a PR is pushed upstream to bitbucket, for a branch matching an issue - the issue would move to the Code Review state. But that is our only point of friction, and one day I'll get off my rear and make our robot do it.

Re: GitHub and Jira Software Integration

#187

Post by nojvek »

dominotw wrote: post #180
bicubic wrote: post #142

Earlier quoted context omitted.

I think it's less a sign of how bad JIRA is, and more how bad project management and project managers are in software development. JIRA can be a decent tool. The issue is the way that 90% of all businesses big and small use it, is just so that managers can shrug off any responsibility for understanding the projects they're managing, and wall themselves off in JIRA bureaucracy. Engineers have not taken too kindly to i…

I've never seen a JIRA installation that isn't slow as hell. Project Manager types dont mind JIRA slowness for some reason. Prbly have too much time in their meetings to sit and wait around.

JIRA is slooooooooooow. I don’t think any fancy integration can fix that slowness if their APIs are just snail slow.

On the other hand JIRA UX and moreso Atlassian UX needs a lot of work. A number of common things take wayyyy too many clicks. It’s hard to discover etc. A good integration can definitely fix that mess.

GitHub knows how to do good simple UX.

Re: GitHub and Jira Software Integration

#188

Post by Spivak »

braythwayt wrote: post #167
kasey_junk wrote: post #37

Earlier quoted context omitted.

It’s a sign of how bad JIRA is. The tool is so bad that people (including me) want the integrations to be hard simply to have a reason not to use it.

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 someone from the engineering side builds something for it -- "why, oh god why are you trying to extend its life?!?"

Re: GitHub and Jira Software Integration

#189

Post by Klathmon »

castlecrasher2 wrote: post #100
chii wrote: post #92

Earlier quoted context omitted.

all of those problems you have aren't inherently a problem with the Jira product. They are organizational problems, management problems, and communication problems. If you have any of those problems, replacing Jira with another issue tracker will not solve it. Jira gets the flac, because but the problems isn't Jira.

I agree. One of my previous companies used Jira and it was absolutely fantastic because one project manager had a clear vision for it and implemented it and the other PMs planned sprints inside it.

yeah i've just recently started heavily using it for the first time in a few years, and it's not bad!

It has a fair share of issues (it's SO SLOW to do just about everything, and the text editor annoys me to no end!), but overall I think it's making me more productive and it's a lot easier to keep track of what i'm doing, what i've done, and what still needs to be done.

Re: GitHub and Jira Software Integration

#190

Post by dsumenkovic »

singingfish wrote: post #156
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…

My work forces me to use Jira. It could be worse (and it has been better), but it's not great. What gitlab really has going for it is the really really useful CI decently integrated with git. If that's your primary conern then the fact that it gives you a reasonable wiki, issue tracker and other stuff on top is just well-enough prepared icing.

Hello, Community Advocate from GitLab here. Thanks for mentioning our CI and other features.

Since we always care about transparency, everyone can read more about it here https://about.gitlab.com/features/gitlab-ci-cd/. Also to mention the documentation where you can read about the first steps towards your GitLab CI/CD journey https://docs.gitlab.com/ee/ci/

Post reply on HN