3 ms·
For my company which went from its internal hand rolled ticketing system to Jira, Azure, etc. the big issue is that our hand rolled system, even though it had l
by rhaway84773 4y ago
For my company which went from its internal hand rolled ticketing system to Jira, Azure, etc. the big issue is that our hand rolled system, even though it had limited features, was significantly more suited to our needs.
It was much faster, had the exact fields we needed, and the exact workflow we wanted. It provided email alerts using the rules thst made sense for us and did I mention it was ridiculously faster?
We went from a single developer probably spending a few weeks in a year to maintain/augment a ticketing system that worked really great for us, to paying hundreds of thousands for something that doesn’t work well at all.
- kiratp 4y agoSometimes it’s better to just change your workflow to match the tool if that avoids you having to build and maintain your own ticketing system
- figassis 4y agoProblem with this is false advertising. Often, you buy a tool because its website says can do A and B, and do does the sales rep. Then you deploy it and realize it really only does C, and if you squint at it hard enough you can kinda see A and B if you pay extra and spend months customizing it. Growth at all costs mindset makes companies lie do they don’t lose a single lead, then try to lock/beat them into submission and pretend this was always the agreement.
- supportlocal4h 4y agoSure. You take the two ladies who built and maintain your homegrown system and you run them through 6 months of training on Actions and Pipelines and Agents along with two other employees, then give them a Director and an official dept like "DevOps". Now you're ready for a new workflow. See all the hassle and money you've saved?
- tough 4y agoCapitalism winning, it's sufferers loosing. Just another day