We use the Asset feature, having migrated to it from SYSAID.

I assume your powershell script will be used to build a CSV of all your
assets. You'll be able to import this CSV directly into Assets in RT. There
is a plugin to make this super easy:

You will obviously need to do some planning and configuration up front to
ensure your specific Asset database has the Custom Fields you need, and
you'll want to configure your assets catalog lifecycle(s) just like you
would have configured your RT queue lifecycles.

The only tricky thing we are facing at the moment is adding an asset to a
ticket. By default it is easy adding a ticket to an asset (basically: open
the asset, click "Create Linked Ticket" from Actions) but there isn't a
default set up for linking an asset to an existing ticket. Well, there is,
but the searchable text entry requires you to know the asset number in order
to add it, which isn't too useful. But imo this is a solveable problem, I'll
post when I have figured it out.

Other than that do you have any specific questions about Assets in RT?

View this message in context: 
Sent from the Request Tracker - User mailing list archive at Nabble.com.
RT 4.4 and RTIR training sessions, and a new workshop day! 
* Los Angeles - January 9-11 2017

Reply via email to