Automation rule to assign component based on description

[Patricia Johansson]

Hi community!

We have a project for user access and have added various internal and 3rd party tools as components.

I'm wondering if there is a way to create an automation rule that will collect info from the description and assign a component based on it.

For example if description contains "Facebook" assign the Facebook component, I could to this with multiple IF conditions but wondering if there is a smarter way where it will just check if it matches any existing and assign.

I know I can use {{issue.components.name}} but that would only access components that are already added to the issue in question. So is there a way to query the components on a project level instead?

[Bill Sheboy]

Hi @Patricia Johansson 

One way to do this would be to call the REST API to get all the components for the project, and then iterate over them (or build a single search expression with reg ex), search for them in the description, and add the components that you find (using a JSON advanced edit).

I haven't tried this although it seems possible as it would use built-in rule features.

Kind regards,
Bill