81–90 of 222 posts
I noticed absolutely no change in Github's product after the Microsoft news, and I'm 99% sure there will be no appreciable change after this news settles. I'm 100% sure that people are going to freak out and waste their time migrating to BitBucket or GitLab for the wrong reasons. As a Github user, there are a few things Github does that makes me unhappy, like not hyperlinking static text when they should, but who the…
Earlier 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…
Earlier quoted context omitted.
I think it depends on how it's configured and on the team's workflow. It really sucked at my second to last job, but at my most recent job it was reasonably usable, in that about half the time it was better than a comparable tool like Pivotal Tracker or Asana, and about half the time it was worse. A good and bad thing about it is that it isn't a typical single page app - good because it has fewer glitches and bad bec…
You may be right, pivotal might be even worse. Haven't used Asana.
I see a lot of people complaining about JIRA in this thread, so here's my take: - I've used Trello, GitHub Projects/Issues, and other Project Management software; - While JIRA has a steep learning curve and is generally unpleasant to use, it is far and away the most customizable and powerful PM software I have used; - Despite JIRA's poor design choices and UX clunkiness, it is so powerful that I wouldn't use anything…
(Trac can often be customized with 10 lines of simple Python (or CSS, HTML, JS) dropped as a single file into the plugin folder and you're done. It's the hacker's bug tracker. And it's fast and quite easy to use. I wonder why it's not more popular anymore.)
Can we use this post and maybe discuss possible alternatives to JIRA?
However, I've used Jira previously and it worked just fine for me and the team. YMMV
I know that my experience is by definition limited but across multiple companies & industries the use of JIRA has been uniformly an anti/pattern. GitHub issues on the other hand have never been a negative. The only reason I bring this up is that I think this is an unmitigated bad feature. The only pushback I have at times in an org is the moat between JIRA & Github
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.
People complain not only it's complicated but it is slow and overloaded with unnecessary features. Can you open up create a new ticket window and how many features and fields do you count?
Earlier quoted context omitted.
You may be right, pivotal might be even worse. Haven't used Asana.
I have a lot of respect for Pivotal Tracker. It's a really elegant design, it is just missing a good detail view on issues, like GitHub's with history, comments, convenient deep linking, markdown, syntax highlighting, integrations, etc. Trello has a good detailed view for its cards, but not as good as GitHub.
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?
- 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 products is fundamentally different than dealing with customer service items. Just as a specific, issues in JIRA are a terrible way to capture the vision and mission of a new feature. They are further a terrible way to capture requirements which in any other system would be versioned along with the software they define.
- the customization of workflows encourages teams to think of every component as a fungible unit. If you don't define 'workflows' and instead prioritize around results, you can motivate teams to operate in their best ways. If you build complicated or bespoke workflows in JIRA you operate in a way that presumes that all teams and all situations can be put in the same box.
- JIRA, especially in its most customized versions, implies that you can replace normal human communications, conversations, emails, chats, with a Platonic ideal of tickets. Yet tickets are a bad mechanism for spreading big picture ideals and an even worse mechanism for spreading specific details of a functional specification (no testability, no atomicity with software change, etc).
- JIRA's customizability leads people to think that the right thing to do with their project management teams is to define standardized workflows, automated integrations, normalized schemas for issues, and the like. Instead of doing the hard work of aligning priorities Project Managers get caught up in the minutia of making sure tickets are in the proper form or that developers have moved tickets through the correct statuses.
All told, this is one of those cases where worse is better. A title, a comment box and a set of tags largely allow you to systematically capture everything you need to capture and allow a qualified project manager to do their job. Github issues does this, JIRA out of the box does this, Bugzilla and FogBugz all do this. I only ever run into problems with JIRA, so I can only extrapolate from experience that it is something about JIRA that leads Project Managers to spend less time with legal pads and more times futzing with JIRA.
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…
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.
Personally I’m a fan of a physical Kanban board. This definitely scales far worse than JIRA does.