Force people (clients) through subscriptions when creating tickets (etc)
Page: 1
Recent posts in this topic
Pro
I'm getting tired of clients creating tickets and then complaining that they aren't acted upon, because no one received notification. It is poor to assume that a client will take the time to learn how this system works (though tooltips or the like would be nice).
It should be possible to set a default behavior that a client must make subscription choices for a ticket, while creating/submitting a ticket.
It should be possible to set a default behavior that a client must make subscription choices for a ticket, while creating/submitting a ticket.
It is poor to assume that a client would take time to learn the system; I have a hard time getting EMPLOYEES to take time to learn the system. Suggestion (and we have not yet implemented this because we don't need everything on the web interface and have not yet figured out how to modify it) - clients enter tickets via the web interface
- tickets entered via the web interface goto a project called "Web Requests"
- We monitor the Web Request project and assign/move tickets as appropriate
- tickets entered via the web interface goto a project called "Web Requests"
- We monitor the Web Request project and assign/move tickets as appropriate
