Discussions happening on LinkedIn right [NOW](https://www.linkedin.com/posts/stephen-lemp_i-wanted-to-build-something-thatd-be-popular-share-7386068750275342337-pxgU?utm_source=share&utm_medium=member_desktop&rcm=ACoAAA1Yt74BKW4bLlqvWuSM2JOVKEORPscNR3s) I wanted to build something that'd be popular with IT teams supporting NetSuite end users... I thought I'd create a template in ClickUp for how you track all your tickets, problems, changes, and knowledge... I sat down to work it all out with ChatGPT by my side... And I came down to this: 1️⃣ One list - call it *Tickets* 📧 Email forwarding so emails to [email protected] create a ticket 🗂️ 5 columns (grouped by status, so maybe you could say 6 data points) ✨ ... and that's it Just get a system where you can clearly identify what is on who's plate, and knock those tickets out! Start simple today... \*Build on it tomorrow... caveat: if you started simple yesterday, build on it today. BTW, my 5 list columns were: - Name - so you know at a glance what you're looking at - Assignee - so you know who has the ball - Requester - so you know who you're dealing with - Date Updated - so you know when this thing was last updated (and can find old ones that you should probably provide an update on) - Created Date - so you get the age of it - Ticket Type - an add-on categorization stating if this is an Incident or a Service Request, just because I really like that one. You could probably leave this off, but it is useful for driving SOPs down the road. From my years in providing IT support, I've found the one easiest driver to prioritize tickets (I'm talking about tickets now, not projects that merit resource allocation) is age. So, those dates really drive things for me. ✅ Tickets get resolved ASAP ✅ "Problems" and "Changes" get logged if it's not going to be solved soon We'll add on to this later this week, so stay tuned! ![[Basic Ticketing System - ClickUp.png]]]]