Assets fields

[Martina Bassi]

Hello, 

I have an object schema which contains two object types: Area and Steps.
Area is where (e.g: the production line) the problem has been found and steps are the phases in the production line (e.g: assembly #1, assembly #2, ...)
I have several areas and for each area I have different steps (as attributes and connected through reference). E.g:
AREA = AREA A --> STEP s1, STEP s2, STEP s3, STEP s4
AREA = AREA B --> STEP s1, STEP s4
AREA = AREA C --> STEP s2, STEP s3, STEP s4

I want to create a form with Area and Step fields. The fields should be assets fields and should be conditional. 
I mean:
if "field Area = AREA A", then possible steps are s1, s2, s3, s4
if "field Area = AREA B", then possible steps are s1, s4
if "field Area = AREA C", then possible steps are s2, s3, s4

Is that possible? How to do that?

Thank you,
Martina

[Valerie Knapp · Accepted solution]

Hi @Martina Bassi , thanks for your question.

It should be possible, yes, a configuration like this, where you can filter the options in a question based on a previous input - https://support.atlassian.com/jira-service-management-cloud/docs/configure-the-assets-object-field/ 

This section here explains what to do - 

Use the Filter Issue Scope (AQL) field

Use the Filter Issue Scope (AQL) field to filter your data using information from within the issue itself - based on other Assets object fields or Jira system fields that contain information about the issue.

This field includes validation - correct AQL syntax will be marked with a while incorrect AQL statements will be marked with a .

This field is optional. You can enable Display a default object when this field appears in a customer portal to automatically display an object in this field.

You can use placeholders in this field. Learn more about placeholders.

Filter using object fields from within the issue

You can use the Filter Issue Scope (AQL) field to reference Assets object fields from within the issue. This can be used to link together two or more Assets object fields and create a cascading list.

For example, if you wanted to create an Assets object field that only displays certain models of laptop based on the manufacturer you’ve selected in another custom field, you would create two separate Assets object fields.

Create your first Assets object field and name it “Manufacturer”. Configure the field to show only “Manufacturer” objects retrieved from Assets by setting the Filter Scope (AQL) to objectType = “Manufacturer”.

Now create the second Assets object field and name it “Model”. Configure the Filter Issue Scope (AQL) to show only the models of laptop from the manufacturer field in the issue by typing objectType = “Laptop” AND Manufacturer = ${customfield_xxxxx.label} where “xxxxx” is the custom field ID of the “Manufacturer” custom field.

Now the “Model” field will show only the laptops that correspond to that manufacturer.

Basically, you will need two Assets custom fields, one for the Area and the other for the Steps. Inside of the Steps, you will need to filter on the Area selected to allow only those options to be displayed.

Hope this helps.

Cheers

[Martina Bassi]

Thank you Valerie, really appreciated!

[Valerie Knapp]

@Martina Bassi , possiamo darti una mano con questo, tipo Flavio o Roberto dovrebbero essere in grado di farlo