91–100 of 530 posts
1. It is dog slow. 2. It is dog slow. 3. It is dog slow. ... When my team had an important as-quickly-as-possible sprint, we dropped Jira and switched to Google Docs as it was much easier and faster than Jira. My conclusion was that Jira doesn't do much for developers that can't be done in some Google Docs/Sheets.
We had a product manager who used to write tickets in OneNote and then copy and paste into JIRA when things were quieter in the evening.
It always seems to me that Jira was used to produce Jira itself and that's why it turned out this way.
Same goes for Asana and Slack.
I am reading this comment thread and honestly I don't know that I agree. I think JIRA, like most tools, is as good or bad as you make it. I've been at numerous companies using JIRA that don't seem to have most of the issues referenced here. The only thing I've ever felt like JIRA really lacked in was in a good UX for embedding code snippets or other technical details into issue comments. Native support for Markdown i…
The biggest problem I have, by far, is just how easy it is to create bureaucracy-intense workflows in JIRA and make management believe these are absolutely necessary. Most developers do not need this info, and do not have the power to easily change things. All the fields when making a simple ticket, the dozens of sub-tasks, the ticket inside a ticket inside a ticket. I would believe this is not impossible to avoid, but I do feel a simpler structure using labels, milestones and issue tracker is far, far easier and less prone to being misused. GitLab and Github can both do this as far as I know.
And sure, JIRA integrates nicely with other products (Bitbucket, Bamboo, Confluence). Other products have these integrations on a more modular level and still load faster and have small QoL differences over JIRA. Maybe big corps need a bit more, but JIRA seems to be too focused on managers and suffers from feature creep to the detriment of user experience.
I am reading this comment thread and honestly I don't know that I agree. I think JIRA, like most tools, is as good or bad as you make it. I've been at numerous companies using JIRA that don't seem to have most of the issues referenced here. The only thing I've ever felt like JIRA really lacked in was in a good UX for embedding code snippets or other technical details into issue comments. Native support for Markdown i…
Native support for Markdown in comments would be a good win. In the Atlassian ecosystem, the markup languages are constrained by the following equation: JIRA Markup != Confluence Markup != Bitbucket Markup
- backticks when creating a Jira ticket, e.g. `hello`
- double curly-braces when editing a Jira ticket, e.g. {{hello}}
... or vice versa. I cannot honestly remember which way round it is. Of the complaints I have about Jira this is probably the least annoying - but it really shows how irritating the product is.
Every bullet point says "Missing...", but I feel like the main issue about Jira is that it has waaay to many features, and that it's super slow! The only bullet point I do agree with, is that Jira is missing an easy (or IMHO a minimalist / simple) interface. The tool is a mess, and the people using it are probably also using it in the wrong way, making the whole situation way worse. Don't get me wrong, I like Jira to…
Every bullet point says "Missing...", but I feel like the main issue about Jira is that it has waaay to many features, and that it's super slow! The only bullet point I do agree with, is that Jira is missing an easy (or IMHO a minimalist / simple) interface. The tool is a mess, and the people using it are probably also using it in the wrong way, making the whole situation way worse. Don't get me wrong, I like Jira to…
I think you are right: the SLOWNESS is a killer. In fact, I think it is THE show-stopper flaw. I recently succeeded in an 18-month-long effort to coordinate moving off of JIRA at work. We moved to clubhouse.io and it's been great. We were also looking closely at GitHub Issues + something like ZenHub for the missing project-management features — and that would have been great, too. As soon as we moved off of JIRA, the…
I think there are multiple clones of JIRA that literally just focus on the performance part. I think at this point it's unrealistic to expect major performance improvements in a timely fashion with JIRA.
Every project I’ve ever worked on, features are finished, apps and websites are shipped, clients are happy and pay the bills, yet the burn down just goes straight to the right and never down. Sometimes right and up if people added more tickets during the sprint.
We look at it at the end of the sprint and say ah well and continue on our way.
Then sometimes a PM type decides it’s a problem but nothing ever changes it.