Atlassian cripples’ Jira automation for all but enterprise customers

Post by AtlasBarfed » Thu, Sep 21, 2023, 4:45 PM UTC

logicchains wrote: post #51

Aurornis wrote: post #33

Earlier quoted context omitted.

> I never saw any developer who was happy about Jira. We did a clean Jira setup from scratch as set up by developers for developers. It was fine. It wasn’t until the company hired full time TPMs who made it unnecessarily complicated with an endless list of plugins and processes that it got to be miserable. The real killer was the way they wanted us to use it: They declared that only TPMs could move tickets, and only…

>Repeat those meetings 3X a week and I developed a visceral objection to Jira. Only later did I realize that what I hated most was actually the pomp and ceremony that came with Jira-toting TPMs Jira's like guns: it can be used for good or evil. But given how bad the worst case can be, would you really want to leave a bunch of rifles lying around your company?

Post by esafak » Thu, Sep 21, 2023, 5:27 PM UTC

criley2 wrote: post #20

asoneth wrote: post #15

Earlier quoted context omitted.

In my experience at mid-sized companies the decision is usually made by the development teams themselves who have a choice along a spectrum between a proprietary SAAS solution that may end up costing the company unpredictable amounts of money in the future on one end and a self-hosted open source solution that we have to trust the IT/devops folks to maintain competently on the other. Also in my experience, the compan…

The cold hard math that engineers never want to do is the one involving their own salary. On levels.fyi devops is median $150k in the US, and at that price it means they cost the company a lot more including benefits, taxes, etc. If a "crappy" tool costs $10k/mo for the team and doesn't require much or any devops time to setup and maintain, it's likely cheaper than the $0/mo opensource but requires part or full time…

Post by esafak » Thu, Sep 21, 2023, 5:32 PM UTC

hotnfresh wrote: post #59

criley2 wrote: post #20

Earlier quoted context omitted.

The cold hard math that engineers never want to do is the one involving their own salary. On levels.fyi devops is median $150k in the US, and at that price it means they cost the company a lot more including benefits, taxes, etc. If a "crappy" tool costs $10k/mo for the team and doesn't require much or any devops time to setup and maintain, it's likely cheaper than the $0/mo opensource but requires part or full time…

What’s left out is accounting of the time the paid tool wastes. Ten seconds here, a minute there, two seconds another place. If the open source solution is in fact the more productive tool (nb it might not be ) then $20,000 in dev time to babysit open source might be cheaper than the $10,000 paid tool—because that tool is wasting more than $10,000 in productivity, it’s just harder to see.

Post by steve1977 » Thu, Sep 21, 2023, 6:03 PM UTC

gumballindie wrote: post #53

Just like code smells, there are workplace smells - practices that indicate a place is meh. Use of atlassian Jira is one such smell.

Post by hef19898 » Thu, Sep 21, 2023, 6:51 PM UTC

steve1977 wrote: post #77

gumballindie wrote: post #53

Just like code smells, there are workplace smells - practices that indicate a place is meh. Use of atlassian Jira is one such smell.

My blacklist: - Jira - Confluence - Salesforce - Anything SAP, but especially HR products - MS Teams - MS Sharepoint