Difference between revisions of "Implement Email Ticket System"
(→'''Done When''') |
(→'''Discussion''') |
||
| Line 20: | Line 20: | ||
=='''Discussion'''== | =='''Discussion'''== | ||
| − | << | + | An update on this, most of the user accounts have been created, just a couple of testing things to be done. Like create <email>43d3127eea6a8c92e8418bcf3f2f44db</email> account and have <email>e2ce7c4406065cac848ad4e72d7fdfed</email> emails go there as well as where they currently go so that in case there is a problem the emails are still going to people who currently deal with them. I also need to create some tutorials for this, and teach the rest of the people that are going to use it. |
=='''Task Lead'''== | =='''Task Lead'''== | ||
Revision as of 20:02, 3 September 2007
Description
Implement the OTRS email ticketing software
Why?
To implement a scalable solution for staff and community members to respond to and track help, support, and catch-all emails.
Done When
-
The software has been installed - The software has been configured
-
goes to OTRS.
-
- All staff have been trained
- Review if this works for everyone
Useful Links
>
Discussion
An update on this, most of the user accounts have been created, just a couple of testing things to be done. Like create 
account and have 
emails go there as well as where they currently go so that in case there is a problem the emails are still going to people who currently deal with them. I also need to create some tutorials for this, and teach the rest of the people that are going to use it.
Task Lead
- Task Lead: Scott Keeler
- Ethan Devenport
- Simon Koldyk
Resource Estimate
- Pair Days: 2
- Dollar Cost @ PairDayCost per pair day:
Evaluator
- Evaluator:
Task Evaluation
- How the task went:
- Sign off Person:
- Sign off Date:
