Jira automation rule for two custom single select fields Cause (Level 1) and Cause (Level 2)

[BiruteK]

Jira automation rule for two custom single select fields Cause (Level 1) and Cause (Level 2)

I have created Custom field Cause (Level 1) with dropdown options: People, Process, External, Systems and Infrastructure

Another Custom Field Cause (Level 2) with all the subcategories list)

How to add automation Rule For dependent fields, if Cause (Level 1) = People, then Cause (Level 2) =

Poor behaviour

Inadequate management control and supervision of staff

Inadequate training and competence

Inappropriate remuneration model

Human error

Key person/knowledge dependency

Insufficient or unavailable resources

Third party

if Cause (Level 1) = Process, then Cause (Level 2) =

Inadequate policies or procedure manuals

Inadequate design of process

Inadequate design of product

Inadequate monitoring, reporting and control management

Change execution failure

Mismanagement of records

Poor data quality or process

Model error or misapplication

Incorrect documentation (e.g. customer, product, employee)

Legislative or regulatory

If Cause (Level 1) = Systems and Infrastructure then Cause (Level 2) =

Inadequate hardware, software or network capabilities

Hardware, software or network failure

Hardware, software or network malfunction Inadequate hardware, software or network maintenance

Inadequate external hardware, software or network support

Non-IT infrastructure (e.g. utilities) failure

Non-IT infrastructure (e.g. utilities) outage Inadequate access management

Inadequate physical security

if Cause (Level 1) = External, then Cause (Level 2) =

Legislative or regulatory change

Market infrastructure change

Natural disasters

Man-made disasters (non-malicious)

Criminal/terrorist activities

Social engineering and identity theft

Civil and political activities

Failure of third party to deliver contracted service level

Cause (Level 1)

[Dick]

Hi @BiruteK Welcome to the Atlassian Community

I'm sorry to say that by restricting yourself to two custom fields, you're setting yourself up for database disaster. As @Karan Sachdev mentions, use cascading select list. This is the only way that reports derived from it will be interpretable in only one way. 

[Salih Tuç]

You can use if/else block on the automation.

On the first if condition, you can select two fields' combinations and you can add else-if for others. For more details on the condition, you can check the related documentation.

[BiruteK]

Are you Able to provide more details for this rule, I started as instructed by you, but not sure how to continue? 

[Karan Sachdev]

Hey Birutek,

Welcome to Community!

Do you want to display only the specified values for level 2 based on the selection in level 1? For example, if the users select People in level 1, they should only see the below values for Level 2:

Poor behaviour, Inadequate management control and supervision of staff, Inadequate training and competence, Inappropriate remuneration model, Human error, Key person/knowledge dependency, Insufficient or unavailable resources, Third party.

If so, you may consider creating a custom field of cascaded select list type. Your Level 1 options will be the parent values, and level 2 values will be the child values against each parent value.

Here's a KB article from Jira data center but it's valid for cloud as well: https://confluence.atlassian.com/jirakb/jira-data-center-how-to-create-dependent-cascading-lists-in-jira-1142426572.html

[BiruteK]

Karan Sachdev 

Yes this is correct, however Cascading is not an option for me , because I need to have two separate fields in the issue for reporting purposes