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

91–100 of 222 posts

Re: GitHub and Jira Software Integration

#91

Post by kasey_junk »

drb91 wrote: post #90
kasey_junk wrote: post #48

Earlier quoted context omitted.

The worst part is there is no evidence it makes managements job easier. The saying is JIRA is yo project management what PowerPoint is to public speaking. For people who are good it can marginally improve the output but for most people it’s an easy way to wank away your time convincing yourself you are working on the right thing as you ignore the real issues.

I’m not entirely convinced eg Trello or Asana would do much better here, and you need to organize planned work somewhere. Personally I’m a fan of a physical Kanban board. This definitely scales far worse than JIRA does.

> his definitely scales far worse than JIRA does.

Does it? I think there are compelling arguments against it wrt remote employees. But I've seen no evidence that once you get bigger than a project that requires more than a physical Kanban boards any project synchronization becomes a farcical activity.

Re: GitHub and Jira Software Integration

#92

Post by chii »

kasey_junk wrote: post #89
zuern wrote: post #74

Earlier quoted context omitted.

Just curious, what do you think is so bad about Jira? I think it's miles ahead of other tools like Rally for example. What's your preference?

JIRA in its out of the box configuration is an adequate issue tracker. Thats never the problem. The problem falls into a few broad categories: - conflating how you interact with issues (bugs, security events, new client on-boarding, etc) and how you do product development (prospecting, requirements analysis, systems design, etc). These activities only have a passing relationship with each other. Designing new product…

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.

Re: GitHub and Jira Software Integration

#93

Post by landon32 »

CodeSheikh wrote: post #45

Can we use this post and maybe discuss possible alternatives to JIRA?

https://www.notion.so/

It's like Google Docs + Trello + a Wiki. We use it for our product roadmap and task management, and can easily link to documentation, specs, or discussion all in one platform. I'm a huge fan.

Re: GitHub and Jira Software Integration

#94

Post by jfoutz »

smokeyj wrote: post #77
zuern wrote: post #74

Earlier quoted context omitted.

Just curious, what do you think is so bad about Jira? I think it's miles ahead of other tools like Rally for example. What's your preference?

People who hate JIRA never had to manage other developers or coordinate work across teams. It's not a product that anyone loves but what the heck are you expecting?

With a pure jira approach, I would expect engineers to do what they think is best in the moment, and log something that vaguely matches the requirements laid out in the ticket. Essentially ineffective management of developer time.

Re: GitHub and Jira Software Integration

#95

Post by chii »

qaq wrote: post #80
lucidone wrote: post #76

Earlier quoted context omitted.

There are a million project management apps out there because it's basically all CRUD.

There are a million project management apps that a small team can use and there is 0 aside from Jira that large enterprises can use.

> 0 aside from Jira that large enterprises can use.

that's because the complaints against Jira (being infinitely customizable and has lots of enterprise features) are the very things that a startup can't do - and perhaps, feel they shouldn't do.

Re: GitHub and Jira Software Integration

#96

Post by kasey_junk »

chii wrote: post #92
kasey_junk wrote: post #89

Earlier quoted context omitted.

JIRA in its out of the box configuration is an adequate issue tracker. Thats never the problem. The problem falls into a few broad categories: - conflating how you interact with issues (bugs, security events, new client on-boarding, etc) and how you do product development (prospecting, requirements analysis, systems design, etc). These activities only have a passing relationship with each other. Designing new product…

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.

But most other systems don't sell that they can solve this problem. If I gave you a web form with a title, a description, a comment section and some tags, would you argue that you could solve those org problems?

Would you spend any time trying to solve the problem in the system?

Re: GitHub and Jira Software Integration

#97

Post by chii »

ochrist wrote: post #57
CodeSheikh wrote: post #46

Earlier quoted context omitted.

Trello

Trello was just bought by Atlassian (the company behind JIRA).

Implying that it's not good simply because it's now owned by Atlassian?

Trello is good for what it's designed for - simple lists of lists of notes.

Re: GitHub and Jira Software Integration

#98

Post by dragonwriter »

qaq wrote: post #80
lucidone wrote: post #76

Earlier quoted context omitted.

There are a million project management apps out there because it's basically all CRUD.

There are a million project management apps that a small team can use and there is 0 aside from Jira that large enterprises can use.

> There are a million project management apps that a small team can use and there is 0 aside from Jira that large enterprises can use.

I'm pretty sure that's wrong; there are large enterprises that use project management software but don't use Jira at all.

Re: GitHub and Jira Software Integration

#99

Post by paulddraper »

zuern wrote: post #74
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.

Just curious, what do you think is so bad about Jira? I think it's miles ahead of other tools like Rally for example. What's your preference?

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 sprints depends on the view you were looking at when you created it.

Plus the UI bad; the whole board gets really squished and becomes essentially unusable if I half-screen it.

Re: GitHub and Jira Software Integration

#100

Post by castlecrasher2 »

chii wrote: post #92
kasey_junk wrote: post #89

Earlier quoted context omitted.

JIRA in its out of the box configuration is an adequate issue tracker. Thats never the problem. The problem falls into a few broad categories: - conflating how you interact with issues (bugs, security events, new client on-boarding, etc) and how you do product development (prospecting, requirements analysis, systems design, etc). These activities only have a passing relationship with each other. Designing new product…

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.
Post reply on HN