As a medium sized manufacturer of custom “things” (medium = maybe 200 per month) who uses rt to track quotes and some other tickety things, we’re considering using rt to track drawings and components that we’re planning to make or have made. Does anyone else use it like this? Is this a bad idea? Is it genius and actually common?
We’d be looking to track the status and revision of drawings (ie issued for approval or issued for construction) and also the status of components (planned, manufactured, delivered etc). Also, we’d like to record QA data about production as custom fields (often as a PDF document).
I’m interested in anyone’s experiences in this direction.
Thanks in advance.
It’s very common for a single RT instance at an organization to be used to track all sorts of different things. Different queues can handle everything from IT support to incoming sales inquiries to accounts receivable. RT has rights at multiple levels so you can allow different sets of users to see only what is important to them.
And if you are making “things”, you might be interested in RT’s assets feature, which is made to track any kind of asset, with links to tickets for work done associated with that asset. People use assets for IT hardware (like laptops), cloud assets (like EC2 servers), and all sorts of other physical objects like medical devices, etc.