Live data from Hacker News

GitHub and Jira Software Integration

blog.github.com

211–220 of 222 posts

Re: GitHub and Jira Software Integration

#211
post #186

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…

Such transition mechanism sounds like 'smart commit'[0] but attached to PR instead? Isn't simpler to just trigger transition directly from commit?

[0] - https://confluence.atlassian.com/bitbucketserver/using-smart...

Re: GitHub and Jira Software Integration

#212
post #117

Earlier quoted context omitted.

My main gripe about JIRA, other than how abysmal it gets when you add a slew of custom fields and workflows all over the place, is that I can't sort on the boards based on all of these fields I've setup. I set priority and severity on every issue, yet I can't sort by those fields in the planner or board, that's infuriating to me.

Check out Jira cloud, you can filter with a single click in the Next-gen UI by issue ower, epic, or label, no JQL required.

Not talking about the search or search results, talking about the Active Sprint board and Backlog.

Re: GitHub and Jira Software Integration

#213
post #118

Earlier quoted context omitted.

JIRA Core is a good issue tracker. However JIRA Agile is a dumpster fire, partly because JIRA Agile reinvents JIRA. Summary field? Yes, but also "Epic Name" field. Status field? Yes, but also "Epic Status" field. Priority field? Yes, but also "Rank" field. Subissues? Yes, but also "Epic Link" field. And then boards and sprints are weird. Boards are supposed to be just views, but then access permissions for closing sp…

I'll tell you a secret, there are no "subissues", there are only issue links and UI represents different kind of links differently ;-).

I'll tell you another secret: Epic Link is something else entirely.

Re: GitHub and Jira Software Integration

#214

Earlier quoted context omitted.

> "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.

Not really. Opinionated software is good when the opinion is something you agree with. When you need the opinionated software to something it wasn't designed for it's frequently really bad. CMake is opinionated. It's built assuming that the build yields an executable file for Windows, Linux or Mac. Try getting CMake to cross-compile for more than one platform at the same time, or build not than one executable and the…

Everything you state as being a "benefit" of Jira's customizability is why devs hate it. The software's features aren't being used to help developers do their jobs, which was the original reason for the product, but to help managers and report fetishists collect reams of unnecessary data points. It is a hindrance to your organization, but at least you get to make sure all those checkboxes are checked.

It sounds like you're either one of the report generators, so it's awesome for you, but all your devs hate it.

Re: GitHub and Jira Software Integration

#215

Earlier quoted context omitted.

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…

There are tools that solve the problems. It's called GitLab Issue Boards or Phabricator.

GitLab Issue Boards tracks capex?

Re: GitHub and Jira Software Integration

#216

This is pretty much every thread. Tool X sucks. No, you set it up incorrectly Tell me why it sucks? Management sucks Maybe your team/team and management is the problem. Oh Hai, GitLab CEO here. We will build whatever it is you are complaining about.

I can't take GitLab seriously until it stops touting itself as a project management tool with its flimsy label-based 'workflow' model.

Re: GitHub and Jira Software Integration

#217
post #122

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.

I think in this text a corporation is being modelled as a single being with a single decision-making capacity. Sort of like how "my brain" forces spicy food on "my intestines", but when you model the two things together as a single human being, then you can confidently state that nobody is forcing me to eat spicy food. Really, all the GP is trying to say is that neither Github nor Jira has any external market forces…

Haha, thank you for this! You must forgive me ("the GP") for being bemused by the textual analysis you have written in defense of my comment!

Re: GitHub and Jira Software Integration

#218
post #169

Earlier quoted context omitted.

What? I have used and i'm using jira for probably 7 years in 3 different companies with 6 different projects. I always took care of our workflow and small issues by the side. Once configured properly (which has nothing do to with magic) it works as advertised. there are a few small issues but not that relevant in daily life. We used atlassian online service and on premise.

I would love to meet you and introduce you to any manager I have in the future (because I"m sure Jira will be reintroduced in my professional career). What were you using Jira for? Are you an engineer committing code daily? What style do your projects usually follow (waterfall, agile, etc)? What source control tracking do you use with Jira? Were you doing burndown charts?

I'm an engineer. Writing code but also doing code review.

I worked with jira and scrump but the last two years I introduced kanban. But those projects have a high level of uncertainty and supportrequests. Which just makes it hard to finish a Sprint.

Always git. Git with GitHub.com, on premise GitHub and selfhosted gitlab.

I do use the reporting Features. It is nice to see the progress. Seeing the backlog shrinking and also the time on how long a ticket is in progress. It helps a little bit of keeping priorities. It also helps showing the management why stuff takes as long as it takes. Especially unplanned work.

Re: GitHub and Jira Software Integration

#219

Earlier quoted context omitted.

It's probably implied that Trello one day will become Jira...

Nah, not really. It was just for information. But Atlassian must have some kind of plan for Trello, and I for one can't guess what that might be.

The plan is to let Trello do what it does best, help people manage anything from organising a wedding to planning software projects.

Re: GitHub and Jira Software Integration

#220
post #118

Earlier quoted context omitted.

I'll tell you a secret, there are no "subissues", there are only issue links and UI represents different kind of links differently ;-).

I'll tell you another secret: Epic Link is something else entirely.

Yep, it's a custom field, purely Agile's feature.
Post reply on HN