>>>>> "Matt" == Matt Disney <[email protected]> writes:
Matt> On Mon, Jun 4, 2012 at 5:03 PM, John Stoffel <[email protected]> wrote: >> >> So which has priority? Making the list handle tickets, or keep the >> discussion? If it's mostly for tickets (in an ah-hoc manner >> currently), then making it into a ticketing system is a good idea. >> Move the discussion off to a new, well publicized list and you're good >> to go. Matt> Difficulty in publicizing a new list is exactly the reason I'm Matt> opposed to breaking the list apart. Most of the messages to the Matt> list are sent by non-subscribers. Over time, we have managed to Matt> get the word out and create a strong internal brand around that Matt> email list. I'm not convinced we can easily reproduce that with Matt> new email lists but I haven't ruled it out. What is the brand for that list? Is this where people send email to get help? In that case, make that default to opening tickets. If it's the default for discussions, then open a new mailing alias for tickets and have someone on your team just forward discussion emails to the ticket list to open tickets at need. >> Don't try to combine them. >> Matt> To be clear, I'm not really combining them, they're already Matt> unified. I'm just trying to extract the requests on that list Matt> out into tickets rather than forwarding them in manually. They're not unified at all, you don't have a ticket system in place. You're trying (not without some justification) to have your cake and eat it too. But they're seperate things. So keep them seperate and decide which current use is more important. John _______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
