71–80 of 251 posts
I still can't believe they invented their own language... but #1 seems like it would have been enough. I hate using JIRA, though, just like I hate using all Atlasssian products, so it would have been nice if FogBugz won.
Having mainly done line of business applications my entire life, I have a slightly different take. Jira won because it was not opinionated. You can use it however you want. FogBugz had the philosophy to make bug entry super easy above anything else. Jira will let a manager define new custom fields and make them all compulsory. It perfectly fits how manager at big companies think. FogBugz provides Completion Date Prob…
I will agree that "intelligent" time tracking features in FogBuz ~4 years ago seemed relatively flaky and random. JIRA's benefits are likely in customization - which is a giant pain for managers in some ways, but it's nice that it can do it, but JIRA is supremely frustrating when editing dashboards. Every time somebody changed a component name, it would break all the underlying queries, etc. I think there's a huge ma…
And yet, "Creating a JIRA task is like going to the fucking DMV." https://twitter.com/jesseherlitz/status/648557144845910016
Does the opposite kind of user exist? Has anyone ever met a fanatical JIRA lover? In my experience there are only people that tolerate JIRA on one side of the spectrum and a bunch of people that hate JIRA on the other side.
A bit off topic, and I know I'm sounding like a condescending jerk here but I mean it: but why do people love bugs so much that they want to purchase an entire database program to track them? I mean, if you have more than 10 bugs that are highly important to keep track of, it seems to me that you have much larger problem than whether to purchase JIRA or FogBugz. I mean, either a bug is important to you so prioritize…
https://github.com/facebook/react/issues
They are using the issue tracker for all sorts of things, and it clearly has value.
> This meant they couldn't use all of the ecosystem and amazing tooling around Java [...] Does anyone else get the same confused feeling whenever they read things like this? Every experience I've had with the Java/JVM ecosystem has been anything but amazing to the point where I now avoid it like the plague. I can't believe I'm that much different than everyone else, but I see this often enough that it makes me wonder…
Nope, just the opposite here. The JVM ecosystem is hands-down my preferred environment for building / deploying pretty much anything.
"Different strokes for different folks" and all that...
Yet FogBugz still feels way easier to use. Every time I'm in an Atlassian product, mainly Stash and JIRA, the UI sucks. I use them several times a week and still get lost. Maybe I'm dumb, but I don't seem to have this problem on other systems. But hey, at least JIRA isn't the craptastic laggy pos that is Podio. Certainly right that I've never seen FogBugz outside of myself or customers. Also, I think the name must hu…
One of the simplest examples I can give is the inconsistent dropdown list. For most (but not all) dropdowns it lists all of the items except the one you currently have selected. This is a departure from every other system I have ever used and find it annoying.
There's an interesting discussion happening on Reddit involving ex-employees of both companies: https://www.reddit.com/r/programming/comments/3n2sc1/why_fog...
An interesting point from that, since everyone likes to bash Wasabi: > "If we hadn't done Wasabi, then we'd have had to rewrite all of FogBugz, and that would've killed the company. Wasabi also gave us stuff that developers are only now rediscovering, like code that executes on both client and server (e.g. via server-side/client-side React), that even gave us a development edge. I've written about this at length ( ht…
http://hanselminutes.com/493/killing-off-wasabi-a-20yr-old-v...
Earlier quoted context omitted.
Does the opposite kind of user exist? Has anyone ever met a fanatical JIRA lover? In my experience there are only people that tolerate JIRA on one side of the spectrum and a bunch of people that hate JIRA on the other side.
I love JIRA and would absolutely advocate for using it over any other tracker. With just a little tweaking (30 minutes or so on a fresh install), I can have it perfectly configured to match my ideal workflow.
There's an interesting discussion happening on Reddit involving ex-employees of both companies: https://www.reddit.com/r/programming/comments/3n2sc1/why_fog...
An interesting point from that, since everyone likes to bash Wasabi: > "If we hadn't done Wasabi, then we'd have had to rewrite all of FogBugz, and that would've killed the company. Wasabi also gave us stuff that developers are only now rediscovering, like code that executes on both client and server (e.g. via server-side/client-side React), that even gave us a development edge. I've written about this at length ( ht…
I have always seen Fogbugz as a support tool first, bug tracking kindof it's what they built for Fogcreek's process(for Copilot support and development). If you did everything like them it probably was a great fit. Jira on the other hand I have always seen as bug tracker.