ITSM Config Item search new field filter

[wheelshot]

Hi,

I've read some posts in here (and this one also: viewtopic.php?f=62&t=22523) but my questionning aint same one.

Is there a way to add more custom fields filter in the "<All>" classes scope?

Im able to add custom fields for a specific class search (using ITSMConfigItem::Frontend::AgentITSMConfigItemSearch###ShowColumnsByClass) and add a "searchable" tag on my new field but what I'd like is that I could do a single search over all classes for my specific new field filter.

I tried adding my field (with 1 as content) in ITSMConfigItem::Frontend::AgentITSMConfigItemSearch###ShowColumns but it seems to have no impact at all on the CI search window.

Any thoughts on what I'm doing wrong?

At the moment, with that limitation, im aiming at 2 scenarios:
1. Im creating a new CI Class that will contain specific CIs
2. Adding my custom field and ask people to do multiple searches for the same field (using search templates of course)

Context is that we have CIs that we wanna tag as something that can be lent to people (computers, hardware, etc.). I'd then create some process or ticket template so that the customer service would get notifications of when something's due, etc. Would there be better way to handle that kind of feature?

Thanks for your help and have a good day!

[wheelshot]

Bump. Any ideas? Thanks for the help

[crythias]

I personally don't have a fully fleshed out idea, but this is what I am thinking :

Add a new state for the CI: borrowed/lent/out, and make a ticket with a pending reminder in a borrowed queue for return date.

Now that I think about this, I might have a personal use for a queue dedicated to scheduled items to resolve in the future.

[wheelshot]

I personally don't have a fully fleshed out idea, but this is what I am thinking :

Add a new state for the CI: borrowed/lent/out, and make a ticket with a pending reminder in a borrowed queue for return date.

Now that I think about this, I might have a personal use for a queue dedicated to scheduled items to resolve in the future.

Makes a lot of sense.

I think i'll go like this:
- Create a new CI class (Cause we got multiple units that would like to use that system to lend stuff and have their own inventory) and assign the right role
- Create a new status "Borrowed"
- Create a new service for that borrowing equipment
- Create a ticket template for agents and customers that will fill up most of the fields.

Planned date will be the date it should be returned by the borrower and pending reminder date will be for the agents handling the service.

Thanks for the brainstorming crythias! Have a good one