How can I limit or validate Asset fields so that users MUST select from the available options?

Question

I plan to allow our Bus System Admins to add and update their own Config Items in the CMDB (in Assets).  However, I want to require some fields and also limit the available options on certain fields.

For instance, if someone creates or edits a laptop record, I'd like to require that they select a valid model - and they should only be able to select from the available models we use (which exist in a separate asset table).

Mark_e8e560 · Answer

Hi A A Ron,

My goal was to allow users direct (but constrained) access into the Assets tables.

Unfortunately, it appears the control I need is just not available in JSM Assets natively.  So I was forced to use a 3rd party solution to provide the functionality i needed.

I'm using the "Stratacom Mobile App" very effectively for this.  They have a very capable screen builder designed for use on mobile devices (supports bar code scanning) but it has now expanded to offer pretty decent screen/form and field control capabilities.  This includes conditionally controlled things like button/screen availability, field visibility, default values, requirements, etc.

If you're looking for a controllable user interface to JSM Assets data, I'd recommend you check it out.

A A Ron Geister _Trundl_ · Answer

@Mark

I would also like to welcome to Atlassian Community!

Are you doing this straight in the Object Schemas? Meaning that the data they entered is being update in the tables and that is where you can't set a requirement?

I have not found a way to require an attribute to be entered in the past directly in the asset schema.

I know some teams use a Jira request to add objects and attributes via JSM form and use automation to populate the data in the the schemas.

This is an article that can help with updating attributes via automation and request form:
https://confluence.atlassian.com/jirakb/how-to-update-asset-object-attribute-using-automation-with-values-from-associated-jira-issue-1085200114.html

I do believe if you are using request forms to populate data from there to assets you can set asset fields and Jira fields as required in the request type.

I hope this helps.

Mark_e8e560 · Answer

Thanks for the response.  I understand referencing the other table, but when I do this, users can still simply leave the field blank or they can type something invalid and choose to create a new model in the table.

I'm guessing I can restrict user ability to add to that table in many cases, although I'm not sure that's ideal in all cases.  Also, it still allows them to leave the field blank.  I don't see a way to set a field as mandatory/required.