We would like to track spare parts usage and their associated costs within Jira Service issues. Would it be reasonable and effective to configure Assets for this purpose?
Hi @Dan Tong,
Welcome to Atlassian Community!
I would say that this is a prime example of what you can use Assets for. It is labeled as a CMDB, but I would say CMDB+ is better. One example of how I used in the past is as a decision tree. Our HR has a need for adding approvers from 2 - 4 different business teams based on the department and this was stored in Assets. Another example I've seen is to keep track of pianos at a university to keep track on their location, cost and the status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.