How to create relationship between two fields without plugin

[Kelly Phillips]

Hi

We have 2 JSM fields, Components (which we use for our teams - each team is a component) and Assignee.
Currently, there are instances where and assignee is changes, but the Component is not updated to the correct team according to who the assignee is.

For example, a item that the Network team is working on, is re-assigned to John Doe who is a service desk technician.  But when it was reassigned, the Component wasn't updated to Service Desk team.  This means that our queue filters (set to Components) does not show this item in the correct queue.

I can create an automation to run when the assignee is changed, which will look at the Component and update it if it's incorrect based on the assignee, something like the below. But it's clunky and doesn't look pretty.

Trigger: When assignee is changed

Then if assignee equals Bruce Wayne, Eddy Brockman, Steve Rogers 

And component does not equal Modern Workplace

Change component to Modern Workplace.

Else if assignee equals Tony Stark, Bruce Banner, Nick Fury

And component does not equal Network & Cloud

Then change component to Network & Cloud

Else if assignee equals John Doe, Jane Duncan, Daffy Duck, Clark Kent

And component does not equal Service Desk

Then change component to Service Desk

 Etc, etc, etc

The issue with this is having to remember to update this rule whenever the team changes.
These fields are also out of the box fields, so they can't be customised.

Is there some way to create/maintain a tablet and point the automation to look at the table?

Or is there another way to do this that is easy to setup and maintain?

[John Funk]

Hi Kelly, 

You can check to see if the Assignee is in a particular role and then update the component based on that. 

[Tuncay Senturk _Snapbytes_]

Hi @Kelly Phillips 

If I get it right, yes, there is a way to better manage this than hardcoding every name in the automation tab. An option is to use Jira Assets.

Create an object schema in Assets (e.g. Team Directory), and add an object type (e.g. Team Member) with attributes: Name (John Doe), Team (Service Desk)

Create an object type Team if you want to reference team details (Components in your case).

In the automation (trigger: when assignee is changed), action: use lookup objects to search for the assignee's team

objectType = "Team Member" and Name = "{{assignee.displayName}}"

then compare the team name to the current Component and update if different.