shaq_mobile wrote:Yeah I think we are trying to avoid a homebaked or open source solution. In the past, when people move on it becomes an issue. Documentation is also tough to keep up to date.
I don't know if it's totally out of the question, but I think they want to go with a pre built solution that would work across multiple colleges.
shaq_mobile wrote:Is there an API for ticket creation? Does it interface with hangouts, email, or slack? Is there any sms functionality?
Aranarth wrote:The problem with ticketing software is 99% of the people writing the software have never used ticketing software to write tickets. (in the real world)
The flows into "the problem with 99% of CTO's is none of them have touch technology outside of a management role"...
and so it goes....
gecko575 wrote:I currently use Jira at work. I like it quite a bit because you can tie it into Slack and get notifications there. Pretty easy to setup your own workflow and overall easy to use. Recommended.
shaq_mobile wrote:Yeah i work at a large university.
Aphasia wrote:I'll throw a hat in for Jira, its nice, and if you want a hosted managed service instead, I've been using ServiceNow for about the last 5 years at various clients, also works quite well, and is also adaptable if you should need it. The problem with as you can read above is that SNOW can be cumbersome unless you know what you want to do. But I would say for a larger org, SNOW can be made to work better, while for smaller orgs, Jira is likely better. Depends on how much time you want to put in to the tool as well.