- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2024 11:10 AM
Our previous implementer created a custom Request to help track specific information about actions taken for CI equipment changes (such as an asset swap due to things like Lost/Stolen/Role change/Break-fix/etc). We are trying to move away from a lot of the customizations that were implemented in the past and are trying to get back to OOB features, in this case making use of the Affected CI table in relation to Incidents. We are starting at endpoints, because this is what upper management wants to report on.
When we use the Affected CIs tab in an Incident ticket, once closed properly, the Affected CIs table record for this incident (and CI) will contain Activities based on the selections made, for example, if the Asset Action was Swap, that is listed as an activity (Asset action Swap), as well as the Swapped CI value (Swapped CI <CI name>).
This is not enough for the reporting management wants, and so I have added a new attribute with the selections that techs would use to define the reason for the Swap (such as Break/Fix - New Asset, Break/Fix InStock Asset, Role Change - New Asset, etc.)
How do I get this other selection made in the Affected CIs tab in an Incident show up in the task_ci record?
Thanks.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2024 12:21 PM
it was added to the task_ci table. Going to do a self face-palm here, as I can just make the field visible on the record view... which is pretty much all I need. The activities are good to track who would have made the change if the ticket was passed around. Sorry for the non-question question, but thanks for the quick reply.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2024 11:44 AM
Just to clarify, have you added this addition field ("swap reason") on the incident record, or the task_ci record?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2024 12:21 PM
it was added to the task_ci table. Going to do a self face-palm here, as I can just make the field visible on the record view... which is pretty much all I need. The activities are good to track who would have made the change if the ticket was passed around. Sorry for the non-question question, but thanks for the quick reply.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2024 12:47 PM
Sometimes you just need someone as a sound board 🙂