News for hackers. Stuff that matters.
Re:Why Fogbugz lost to Jira by command_tab on Thursday October 01, 2015 @03:53PM (#10314183)
And yet, "Creating a JIRA task is like going to the fucking DMV."

https://twitter.com/jesseherlitz/status/648557144845910016

Re:Why Fogbugz lost to Jira by manicdee on Thursday October 01, 2015 @04:57PM (#10314644)
Only if your installation is set up that way. Here's how I create a Jira ticket in my organisation: 1. Click "Create Issue", 2. type in a summary (the headline), 3. type in the detail, 3. Click "Create"

If you have more stuff to fill out, that's an issue with your local configuration. Blame your Jira master, not Jira or Atlassian :D

Re:Why Fogbugz lost to Jira by lugg on Thursday October 01, 2015 @07:08PM (#10315452)
I'm still going to blame Jira/Atlassian for making that workflow possible.

My work flow is exactly the same as yours, yet it still feels clunky, and is quite correctly, a total dog.

Much like, you know, going to the DMV.

Re:Why Fogbugz lost to Jira by brazzledazzle on Thursday October 01, 2015 @07:59PM (#10315690)
You only have to enter two fields in your workflow and it feels clunky? This doesn't jive with my experience at all but perhaps you're on an old version or it's resource starved. Once you start beating up jira or confluence you have to start tweaking defaults and jvm settings to get the most out of it.
Re:Why Fogbugz lost to Jira by lugg on Thursday October 01, 2015 @10:56PM (#10316445)
It's a managed account.

The 2 fields workflow doesn't feel too clunky, but the interface certainly is, and the speed, oh dear lord, the speed. Its just sooo slow.

Re:Why Fogbugz lost to Jira by brazzledazzle on Friday October 02, 2015 @01:09PM (#10319795)
I assume managed account means it's hosted by someone else. Unless it's Atlassian themselves they're probably being cheap and giving it as little resources as possible and it not being on-prem probably contributes to the feeling of slowness.
Re:Why Fogbugz lost to Jira by lugg on Monday October 05, 2015 @06:04PM (#10335339)
> Unless it's Atlassian themselves

It is

> they're probably being cheap and giving it as little resources as possible and

Almost certainly

> it not being on-prem probably contributes to the feeling of slowness.

Sure, all of 150ms of it really adds up.

Re:Why Fogbugz lost to Jira by philliphaydon on Thursday October 01, 2015 @09:44PM (#10316106)
Jeez so many replies to jira hate with. Oh buts how you configure it. Oh its this. It's that. Stop apologising for a shitty product. If a user find it hard. It's failed. End of story.
Re:Why Fogbugz lost to Jira by Strom on Thursday October 01, 2015 @10:17PM (#10316262)
There is no universal solution. Every product will have users who find it hard to use. Speaking out about the fact that you find it manageable is valuable information and may show that there are more users who find it easy to use than not.
Re:Why Fogbugz lost to Jira by philliphaydon on Thursday October 01, 2015 @11:35PM (#10316587)
I agree. Things for some people, they don't work for others. But you cannot blame users and say "oh its how you configured it" "its good out of the box" etc.

If its failed for 1 user, its a shit product. If its a success for 1 user, it's a great product.

It's GOOD for a user to say they find it easy and why.

It's GOOD for a user to say they find it hard and why.

1 helps the user give a product a second chance by learning of his pitfalls.

1 helps the company improve their product to make it easier for more users.

My point is that apologists shouldn't come in here and blame users for a shitty product.

Re:Why Fogbugz lost to Jira by simoncion on Thursday October 01, 2015 @11:59PM (#10316664)
> If its failed for 1 user, its a shit product.

That is a dangerous over-generalization.

Let's say -ferinstance- you have kick-ass, seriously best-at-what-it-does software that's only localized in Japanese, and a uniglot USian attempts to use it. They're gonna have a hard time. The software will very likely fail them, because they will be unable to understand anything they're being told by the software.

Does that make the software shit? No. No, it does not. The software is great, it "just" needs to be localized in order to be great for a wider swath of humanity.

Re:Why Fogbugz lost to Jira by philliphaydon on Friday October 02, 2015 @12:39AM (#10316764)
Maybe I'm being misunderstood.

From the perspective of the user, if the product fails for that user, its a shit product.

I don't mean the product itself is actually shit.

Like I say:

If its works well for a user. It's a great product. If its fails for a user. It's a shit product.

From the perspective of that user.

But we can learn from both the users who like it, and the users who hate it. But we cannot blame the problems the user has, solely on the user.

Re:Why Fogbugz lost to Jira by simoncion on Friday October 02, 2015 @01:05AM (#10316816)
> From the perspective of the user, if the product fails for that user, its a shit product.

Honestly, even this is a hazardous over-generalization.

I've looked at gobs of software that failed to do what I needed it to do. Much of that software was good-to-great at what it was written to do, but it -like a lot of software- wasn't written to do what I needed it to do.

That doesn't make the software shit, that makes it unsuited for my needs. I am -and many others are- clever enough to distinguish between the two categories. :)

Re:Why Fogbugz lost to Jira by mikeryan on Friday October 02, 2015 @10:37AM (#10318827)
If a user find it hard. It's failed. End of story.

Yet Jira is a wildly successful product.

Re:Why Fogbugz lost to Jira by shill on Thursday October 01, 2015 @04:24PM (#10314389)
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.

Re:Why Fogbugz lost to Jira by morgante on Thursday October 01, 2015 @04:34PM (#10314479)
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.

Re:Why Fogbugz lost to Jira by jackhack on Thursday October 01, 2015 @05:37PM (#10314922)
Can you please elaborate on this configuration? What is the general nature of the configuration changes you're making? Or, how is your workflow affecting the product. I ask as I am in an organization right on the cusp of implementing JIRA, and I would love to steer the implementation team toward a more useful configuration than the clunky defaults, with which I've had prior experience.
Re:Why Fogbugz lost to Jira by morgante on Thursday October 01, 2015 @05:49PM (#10315013)
The biggest things for me are:

* Setting up several statuses (more than in the default) to reflect backlog, selected, in progress, testing, deployed

* Creating an appropriate board which splits everything into columns by status and rows by user

* Setting up a few quick filters to find things like anything which has been in the backlog for more than 6 weeks or bugs which haven't seen activity in the last 48 hours

* Integrating GitHub. Being able to kick a ticket over to QA from your commit message is awesome.

Beyond that, I mostly focus on stripping out default things to make the workflow simpler. I don't need my software to enforce that I can't move a ticket to deployed straight from in progress, and stripping out those extra rules makes it easier to deal with.

Re:Why Fogbugz lost to Jira by jackhack on Thursday October 01, 2015 @06:06PM (#10315109)
Much appreciated. That's a great opener for a discussion with our impl. team.
[dead]
Re:Why Fogbugz lost to Jira by morgante on Thursday October 01, 2015 @05:09PM (#10314735)
Yes, I regularly contemplate the possibility that they all secretly hate me for using software which you don't like. All their appreciation and thanks for moving us over to Jira is surely a facade for their secret plot of hate.
Re:Why Fogbugz lost to Jira by dang on Thursday October 01, 2015 @09:02PM (#10315946)
> your cow-orkers hate it, and by extension, you

I'm guessing you meant this as a joke, but such jokes come across as personal attacks, which are not ok here.

Re:Why Fogbugz lost to Jira by dfabulich on Thursday October 01, 2015 @04:59PM (#10314668)
Issue trackers are like utilities, like electricity and water. If they're doing their job, they're invisible. You only notice them when they're broken.

As a result, all issue trackers have more detractors than promotors, with the vast majority of users being neutral.

Re:Why Fogbugz lost to Jira by deckard1 on Thursday October 01, 2015 @05:56PM (#10315059)
I'm far from loving any issue tracker.

That said, I've used RT (holy shit no), Pivotal Tracker (drinks too heavily from the dynamic DOM/JS koolaid, sucking up all RAM and CPU in the known universe), and JIRA. I'd take JIRA over the others.

Re:Why Fogbugz lost to Jira by meej on Thursday October 01, 2015 @06:16PM (#10315160)
I've used Mantis and Bugzilla and I'd also take JIRA over those.

JIRA is the best bug tracking software I've used since I left Microsoft, which was over a decade ago. Sometimes I still miss Raid, particularly it's ability to build complex queries, but also the ability to connect to any team's project. At the time, it was supposedly the only internal tool used throughout the entire company.

Re:Why Fogbugz lost to Jira by michaelt on Thursday October 01, 2015 @05:15PM (#10314780)
Even if you have the world's greatest system to queue for a scarce resource, you're not going to make people happy to queue :)
Re:Why Fogbugz lost to Jira by philliphaydon on Thursday October 01, 2015 @09:45PM (#10316111)
Never met anyone who likes it. Except the replies to this blog post.