ITAM object field requirement dependent on another

Question

Hi,

I have a resource of type “Computer” in object schema “CMDB” with many fields, and I would like some fields (e.g. License Type) to be required or optional, depending on the field “Status” (e.g. if the field “Status” is set to “In Use”, the field “License Type” changes to required).

I would like to be able to create a new resource with a limited number of fields filled in, but when the status changes to “In Use”, some fields must already be filled in. Jira Cloud, if possible, it is better not to use an additional plugin

Mateusz Gostomski · Answer

Let me clarify my question, because what I mean is that you should not be able to set the status “In Use” if you do not fill in the fields that I have set as required for that status. This means that either the status should not be visible for selection, or after selecting it, the message “You have not filled in all the required fields, you cannot set the status ‘in use’” should appear, and the status should return to the previously set one.

Importantly, this field should not work on objects already added, so that I do not change the status of existing objects

Bibek_ikuTeam_ · Answer

@Mateusz Gostomski ,

Welcome to the community, I do not think there is a out of the box feature to support that, what I can think of using an automation (Test) with a custom field to see if that fits your needs.

1. Create a Custom Field:Ensure fields like License Type and Status are configured in your Object Schema (CMDB) under the Computer resource type.

2. Set Up an Automation Rule:Use Automation for Jira to monitor changes to the “Status” field:Go to Project settings > Automation.• Create Rule >

Trigger: “Field value changed” for Status.

Condition: Check if Status is set to “In Use.”

Action: Add a comment or send a notification if the License Type field is empty, prompting the user to fill it in.

3. Optional Validation Check:If more validation is needed, another action can be added to transition the issue back to a prior state or add a label if License Type remains unfilled. This will signal to agents or stakeholders that more information is required.4. Reporting to Track Required Fields:Use Asset Reports or JQL filters to identify assets where “Status” is “In Use” but “License Type” is empty. This way, you can follow up on items that need updating.

While this approach doesn’t fully replicate field requirement conditions, it helps ensure fields like License Type are populated based on changes to Status without additional plugins.

Let me know how it goes

Regards,

Bibek