After using bugzilla, mantis, tfs, jira, gitlab and github, I honestly think that jira is not half bad. In fact I prefer it over gitlab, but I'm alone with this view on the team.
The hatred towards jira is on par with desktop java.
GitHub and Jira Software Integration
101–110 of 222 posts
Re: GitHub and Jira Software Integration
#102Earlier 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?
I like YouTrack
Re: GitHub and Jira Software Integration
#103Earlier quoted context omitted.
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.
It's probably implied that Trello one day will become Jira...
Re: GitHub and Jira Software Integration
#104Earlier 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?
[deleted]
Re: GitHub and Jira Software Integration
#105Earlier quoted context omitted.
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.
How long has your company been using JIRA for? JIRA has a tendency to.... decay. New ticket types are created with custom fields that aren't ever kept up to date. Everyone starts to choose random entries because they have no choice, and no way to add new ones. Once that starts, things fall into chaos because nobody knows the "right" way to file tickets. Tickets soon become immeasurably immeasurable. Projects become c…
That sounds a lot like a human problem, not a tool problem.
Re: GitHub and Jira Software Integration
#106Earlier 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.
That is precisely the point.
Re: GitHub and Jira Software Integration
#107Earlier quoted context omitted.
How long has your company been using JIRA for? JIRA has a tendency to.... decay. New ticket types are created with custom fields that aren't ever kept up to date. Everyone starts to choose random entries because they have no choice, and no way to add new ones. Once that starts, things fall into chaos because nobody knows the "right" way to file tickets. Tickets soon become immeasurably immeasurable. Projects become c…
That sounds a lot like a human problem, not a tool problem.
There's a saying along the lines of, the purpose of a tool is determined by how its users use it. For instance, security dialogs are often useless because users blindly click through. Is this a human problem? Yes, absolutely. Does that mean we can blame users for not using the dialog properly? No, it doesn't. We're trying other approaches now that encourage better behaviors from users.
All that is to say, a human problem is fundamentally a tool problem.
Re: GitHub and Jira Software Integration
#108JIRA 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.
That just means it's ideal for your projects, and maybe even most projects. That doesn't mean it's ideal for all projects though.
To use an obvious analogy, PHP is the most popular web backend language and it's ideal for my project, so you should be using it on your project regardless of what your project is...
Very few people would agree with that.
Re: GitHub and Jira Software Integration
#109Earlier quoted context omitted.
How long has your company been using JIRA for? JIRA has a tendency to.... decay. New ticket types are created with custom fields that aren't ever kept up to date. Everyone starts to choose random entries because they have no choice, and no way to add new ones. Once that starts, things fall into chaos because nobody knows the "right" way to file tickets. Tickets soon become immeasurably immeasurable. Projects become c…
That sounds a lot like a human problem, not a tool problem.
It's an artefact of the tool having too many features.
Re: GitHub and Jira Software Integration
#110Earlier 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?
I manage developers and coordinate work across teams. Can't stand JIRA.
I'm not expecting much. For one this is a space that many engineers sneer at ("product/sales/marketing/not-engineering" is beneath them) and don't really want to work in. Another thing is that many of the individuals responsible for deciding on project management tools are not qualified to do so but think they are and won't apply effort to doing a proper job of evaluating options.