Comment by louiereederson
14 hours ago
jira premium is $15/mo/user for 300 users. you're saying $50k can cover developing the app inclusive of integrations, maintaining it, providing 24/7 service and 3 9s uptime (per the sla)? don't forget compliance and security. maybe the logic is everyone can be fired and replaced with agents?
Atlassian had on premise option already.
All instances I remember seeing were neglected, not updated running on lowest amount of resources. Everyone in company nagging how slo it is but no one wanted to share budget to improve it.
So for me that experiment „it will be better and cheaper building our own JIRA” was already done. It is going to be cost center that no one will want to throw money at.
Yes. $50k goes a long way outside of the Bay Area.
There is no way you would get anything close to as good as JIRA. Your best bet with that budget would be trying to integrate an existing open source on-prem solution (not sure what that alternative is for JIRA).
> There is no way you would get anything close to as good as JIRA.
It would be hard to do worse. A packet of crayons and a scrap of paper is better than JIRA.
1 reply →
Oh please.
Yes, you wouldn't get something near as complicatedas JIRA, but that would be a good thing! Look, it's enterprise software, so I'm sure there's somewhere that needs to have the overcomplicated permissions system otherwise contractors are going to steal everything that isn't bolted down, but most places I've been don't need, and thus don't use most of all of that crap. If the ticket can only go from planned to done by a certain group of users, backed by LDAP... let's just say, I'm not going to miss configuring which group gets which permissions system.
JIRA's the perfect example of disruption, too. Everyone's got their bespoke workflow, and JIRA has to be customizable to suit all of them. Bespoke software just doesn't have to the same way.
Jira is crap, so the bar is low.