Making automations in cmdb

[Dora Judith Martínez Vera]

I would like to know if automations can be done in the cmdb section in jira, for example I added users and I would like that when the user is placed as inactive, they are moved to an inactive group and no longer appear on the list:

Another question is about filtering the incidents of an object. For example, I placed a button where I can select the object for which incidents have been created, but if I created a filter with the name of the objects, for example computers, and then I moved on to cell phones, do I have to change that filter? Is there a way to leave it fixed?

Thank you very much for your attention and I hope you can help me with my questions.

[Rudy Holtkamp · Accepted solution]

Hi @Dora Judith Martínez Vera ,

First of all, there are no groups in your object schema. Looking at your objects, I can see 3 different objecttypes for 'Employees':

• Empleados
• Activos
• Inactivos

You can't move an object from Empleados to Activos or Inactivos because they are different objecttypes and could have different attributes.

So what you can do (and already doing) is to use the status to mark employees active/inactive. Also note that the AQL filters you create can not (*yet*) be saved. I've talked to the JSM team in Barcelona and they ensured me that they are working on it. So next year we should see the possibility to save AQL filters. Currently you could make use of the Confluence macro 'Assets' (That is, if you have Confluence.)

You can create a page and place the macro with an AQL and select all relevant attributes you want to show. Then save the page and you can go back and forward to this page. If you create two pages/use two macros you can separate the Activos & Inactivos empleados.

See also this blog

[Harrison Ponce]

To add on to @Rudy Holtkamp 's answer. I would agree and recommend using the object attribute as the way to "organize" and "classify" your employees.

If for your business processes require or work out better with different object types (personally would not recommend), or you would like to have this ability for other use-cases, there is an open suggestion about this that you can vote, watch, and comment on:

• JSDCLOUD-10000: Ability to move objects to another object type within object schema in Assets