HelpDesk Ticketing System
-
@scottalanmiller said in HelpDesk Ticketing System:
@tiagom said in HelpDesk Ticketing System:
@scottalanmiller What are the odds, they have their own scott miller.
We are everywhere.
At least you're not as common as Mary Miller. Eich, the headaches trying to pin down which Mary Miller you're dealing with.
-
I'd really like to see a tutorial on setting this up. I ran into issues on both centos and ubuntu.
-
@IRJ said in HelpDesk Ticketing System:
I'd really like to see a tutorial on setting this up. I ran into issues on both centos and ubuntu.
I might be able to tackle that. Maybe. If my laptop gets fixed.
-
@travisdh1 said in HelpDesk Ticketing System:
@scottalanmiller said in HelpDesk Ticketing System:
@tiagom said in HelpDesk Ticketing System:
@scottalanmiller What are the odds, they have their own scott miller.
We are everywhere.
At least you're not as common as Mary Miller. Eich, the headaches trying to pin down which Mary Miller you're dealing with.
Common enough that I always use my middle name. My dad was one of 35 Thomas Millers where he worked. My name is common enough that I've been forced to call myself Alan at jobs before.
-
Why not build a ticketing system?
-
What about the options mentioned in this article?
-
@FrostyPhoenix said in HelpDesk Ticketing System:
Why not build a ticketing system?
Development costs a fair bit of money.
Someone has to then maintain and support it.
Further dev if you want to add features which also costs money.
Is the cost of a premade tool over the course of a year more or less than building and hosting your own?Now, a ticketing system is the hub of your business as an IT support firm, so whilst you could build it factoring in budget, features and project managing it to make sure it is secure, reliable, fast for years to come. Is it really worth it?
I've had the exact same conversation in house but with a documentation/client management system which we've chosen to build in house but not after exhausting every other option. It's a very very expensive project but nobody else has built a tool that we really need.
Remember that in terms of cost
This is the per hour cost for 160 hours of working time across a month to have a pre-built product which works amazingly well. So the math has to be done to build a new one from scratch.
-
@FrostyPhoenix said in HelpDesk Ticketing System:
What about the options mentioned in this article?
Under spiceworks they state "Can be difficult to install on Linux, Unix, or VMWare" lol
Mantis Bug Tracker and Bugzilla aren't even help desks
-
@FrostyPhoenix said in HelpDesk Ticketing System:
Why not build a ticketing system?
Certainly an option.
-
@tiagom said in HelpDesk Ticketing System:
@FrostyPhoenix said in HelpDesk Ticketing System:
What about the options mentioned in this article?
Under spiceworks they state "Can be difficult to install on Linux, Unix, or VMWare" lol
Mantis Bug Tracker and Bugzilla aren't even help desks
Not even kinda. LOL
-
@Breffni-Potter said in HelpDesk Ticketing System:
@FrostyPhoenix said in HelpDesk Ticketing System:
Why not build a ticketing system?
Development costs a fair bit of money.
Someone has to then maintain and support it.
Further dev if you want to add features which also costs money.
Is the cost of a premade tool over the course of a year more or less than building and hosting your own?Now, a ticketing system is the hub of your business as an IT support firm, so whilst you could build it factoring in budget, features and project managing it to make sure it is secure, reliable, fast for years to come. Is it really worth it?
I've had the exact same conversation in house but with a documentation/client management system which we've chosen to build in house but not after exhausting every other option. It's a very very expensive project but nobody else has built a tool that we really need.
Remember that in terms of cost
This is the per hour cost for 160 hours of working time across a month to have a pre-built product which works amazingly well. So the math has to be done to build a new one from scratch.
Yeah, development is certainly not cheap.
-
@scottalanmiller said in HelpDesk Ticketing System:
@travisdh1 said in HelpDesk Ticketing System:
@scottalanmiller said in HelpDesk Ticketing System:
@tiagom said in HelpDesk Ticketing System:
@scottalanmiller What are the odds, they have their own scott miller.
We are everywhere.
At least you're not as common as Mary Miller. Eich, the headaches trying to pin down which Mary Miller you're dealing with.
Common enough that I always use my middle name. My dad was one of 35 Thomas Millers where he worked. My name is common enough that I've been forced to call myself Alan at jobs before.
Glad I waited to read your response till this morning, would've given me nightmares.
-
@JaredBusch said in HelpDesk Ticketing System:
@Breffni-Potter said in HelpDesk Ticketing System:
@FrostyPhoenix said in HelpDesk Ticketing System:
Why not build a ticketing system?
Development costs a fair bit of money.
Someone has to then maintain and support it.
Further dev if you want to add features which also costs money.
Is the cost of a premade tool over the course of a year more or less than building and hosting your own?Now, a ticketing system is the hub of your business as an IT support firm, so whilst you could build it factoring in budget, features and project managing it to make sure it is secure, reliable, fast for years to come. Is it really worth it?
I've had the exact same conversation in house but with a documentation/client management system which we've chosen to build in house but not after exhausting every other option. It's a very very expensive project but nobody else has built a tool that we really need.
Remember that in terms of cost
This is the per hour cost for 160 hours of working time across a month to have a pre-built product which works amazingly well. So the math has to be done to build a new one from scratch.
Yeah, development is certainly not cheap.
Instead of developing one, right from scratch, would it be a bad idea to develop one, based on an existing Open Source solution ?
-
@Veet said
Instead of developing one, right from scratch, would it be a bad idea to develop one, based on an existing Open Source solution ?
Because of the nature of software, you kind of need to start from scratch to get what you want, A lot of things have to be re-done and re-written when you take someone else's tool and try to shoe horn it in.
-
@Breffni-Potter said in HelpDesk Ticketing System:
@Veet said
Instead of developing one, right from scratch, would it be a bad idea to develop one, based on an existing Open Source solution ?
Because of the nature of software, you kind of need to start from scratch to get what you want, A lot of things have to be re-done and re-written when you take someone else's tool and try to shoe horn it in.
And when said shoehorning is complete... the code is generally... very messy.
-
@dafyre said in HelpDesk Ticketing System:
@Breffni-Potter said in HelpDesk Ticketing System:
@Veet said
Instead of developing one, right from scratch, would it be a bad idea to develop one, based on an existing Open Source solution ?
Because of the nature of software, you kind of need to start from scratch to get what you want, A lot of things have to be re-done and re-written when you take someone else's tool and try to shoe horn it in.
And when said shoehorning is complete... the code is generally... very messy.
And there are often limitations with what you can change, so before you know it the cost is much higher than starting from scratch with a clean slate.
-
@Veet said in HelpDesk Ticketing System:
@JaredBusch said in HelpDesk Ticketing System:
@Breffni-Potter said in HelpDesk Ticketing System:
@FrostyPhoenix said in HelpDesk Ticketing System:
Why not build a ticketing system?
Development costs a fair bit of money.
Someone has to then maintain and support it.
Further dev if you want to add features which also costs money.
Is the cost of a premade tool over the course of a year more or less than building and hosting your own?Now, a ticketing system is the hub of your business as an IT support firm, so whilst you could build it factoring in budget, features and project managing it to make sure it is secure, reliable, fast for years to come. Is it really worth it?
I've had the exact same conversation in house but with a documentation/client management system which we've chosen to build in house but not after exhausting every other option. It's a very very expensive project but nobody else has built a tool that we really need.
Remember that in terms of cost
This is the per hour cost for 160 hours of working time across a month to have a pre-built product which works amazingly well. So the math has to be done to build a new one from scratch.
Yeah, development is certainly not cheap.
Instead of developing one, right from scratch, would it be a bad idea to develop one, based on an existing Open Source solution ?
Not always a bad idea, but generally. It totally depends on the situation, but "other people's software" takes a long time to learn and once you branch from it, likely you have to maintain their code as well as yours, so the value of the shared project is lost. You have to test, fix, maintain and develop on your own. The benefit to their original code base will often be a huge negative rather than a positive.
In rare cases you might only want to extend, not change or modify, the original and you are very close to what you want with the original... maybe. But I'd say easily 99% of the time, starting from scratch produces a better product with less effort both up front and long term.
-
@Breffni-Potter said in HelpDesk Ticketing System:
@dafyre said in HelpDesk Ticketing System:
@Breffni-Potter said in HelpDesk Ticketing System:
@Veet said
Instead of developing one, right from scratch, would it be a bad idea to develop one, based on an existing Open Source solution ?
Because of the nature of software, you kind of need to start from scratch to get what you want, A lot of things have to be re-done and re-written when you take someone else's tool and try to shoe horn it in.
And when said shoehorning is complete... the code is generally... very messy.
And there are often limitations with what you can change, so before you know it the cost is much higher than starting from scratch with a clean slate.
With most open source, nearly all, there would be no limits. GPL, MIT, AGPL, BSD, Apache and other common licenses guarantee 100% legal flexibility. But you still have to know how to do the coding.
-
@scottalanmiller said
But you still have to know how to do the coding.
And this is the limit. It's not a license limit, it's a limitation on what their base code/program can do.
-
A big concern of changing solutions is the existing tickets. How hard is it to migrate from one solution to another is a question that needs to be asked. I would like to move from Spiceworks to osTicket, but not seeing anything that anyone has done to migrate the tickets. Looks like a script will need to be made to import those old tickets into the new system.
