I think the biggest problem, is anytime you try and create a universal, low/no-code platform that anyone can use, it results in a poorly optimized, sandboxed, half cocked product. Sure, you can do anything with the platform, but half the time it’s like shoving a square peg in a round hole. I have had to write bad code and processes because that is the only way to get somethings done in the platform.
Also, if I go out and custom create an app, like say I create a fully loaded app for HR, and it’s similar to a product they sell, they will charge you for that product.
AlecSadler@sh.itjust.works 3 weeks ago
You might be joking but I honestly think that’s the case. It’s wild to me. I’ve worked for Fortune 500 companies using SNOW and everybody hated it and regularly voiced complaints and issues and yet the company refused to change. Started doing shit like releasing more training docs on how to use it or doing brown bag lunches on SNOW effectiveness.
But ultimately none of that mattered, it is just inherently garbage.
echodot@feddit.uk 3 weeks ago
Well one of the big problems with it is it’s never properly configured. One of the most annoying things that it does is that it generates tasks only when previous tasks are closed, in theory that makes sense but really the result is that you close a task, and then you have to go looking in the ticket queue for the new task it’s just generated, so you can close that one too. Total waste of time.
AlecSadler@sh.itjust.works 3 weeks ago
I guess that makes some sense, I loathe Jira but I think it’s largely because everywhere I’ve worked that uses Jira has poorly customized it and just ruined the experience.