Ticketing and asset management go together. It's easy to see which assets have the most activity (changes or issues) against them, the severity, and the number of occurrences. It's helped me on more than once to identify hotspots for more in-depth investigation. Enforcing the policy of "you can only create a ticket against assets in the inventory" ensures that tickets have useful data and aren't empty or vague. In asset management I can categorize assets data with multiple tags (e.g. in which data center; in which rack; server hardware (e.g. mfger, model, CPU type, memory type, # & types of disks); Linux/Windows server; firewall/switch (including which ports are in use, purpose, by what assets). Review collected by and hosted on G2.com.
At first, creating custom workflows was more difficult and confusing that I expected. We ended up involving Service Desk consultants. Review collected by and hosted on G2.com.