6 ms·

And yet, "Creating a JIRA task is like going to the fucking DMV." https://twitter.com/jesseherlitz/status/648557144845910016 https://twitter.com/jesseherlitz/s

And yet, "Creating a JIRA task is like going to the fucking DMV." https://twitter.com/jesseherlitz/status/648557144845910016 https://twitter.com/jesseherlitz/status/648557144845910016

shill 11y ago
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.
- morgante 11y ago
  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.
  - gaius 11y ago
    Have you considered the possibility that your cow-orkers hate it, and by extension, you?
    - morgante 11y ago
      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.
    - dang 11y ago
      > 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.
  - jackhack 11y ago
    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.
    - morgante 11y ago
      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.
      - jackhack 11y ago
        Much appreciated. That's a great opener for a discussion with our impl. team.
- dfabulich 11y ago
  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.
- michaelt 11y ago
  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 :)
- deckard1 11y ago
  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.
  - meej 11y ago
    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.
- philliphaydon 11y ago
  Never met anyone who likes it. Except the replies to this blog post.
manicdee 11y ago
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
- lugg 11y ago
  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.
  - brazzledazzle 11y ago
    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.
    - lugg 11y ago
      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.
      - brazzledazzle 11y ago
        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.
        lugg 11y ago
        > 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.

And yet, "Creating a JIRA task is like going to the fucking DMV." https://twitter.com/jesseherlitz/status/648557144845910016 https://twitter.com/jesseherlitz/status/648557144845910016

shill 11y ago

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.

morgante 11y ago
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.
- gaius 11y ago
  Have you considered the possibility that your cow-orkers hate it, and by extension, you?
  - morgante 11y ago
    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.
  - dang 11y ago
    > 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.
- jackhack 11y ago
  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.
  - morgante 11y ago
    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.
    - jackhack 11y ago
      Much appreciated. That's a great opener for a discussion with our impl. team.
dfabulich 11y ago
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.
michaelt 11y ago
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 :)
deckard1 11y ago
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.
- meej 11y ago
  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.
philliphaydon 11y ago
Never met anyone who likes it. Except the replies to this blog post.

manicdee 11y ago

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

lugg 11y ago
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.
- brazzledazzle 11y ago
  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.
  - lugg 11y ago
    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.
    - brazzledazzle 11y ago
      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.
      - lugg 11y ago
        > 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.