Automate owner team according to component in Jira

Question

Is there a way to create an automation in Jira that will allow me to change the team field in an issue according to the "component" that was filled in the issue.

Meaning automatically taking the "Owner Team" from Compass and incorporating in Jira as an automation so that the person creating the issue won't have to know which team is should be assigned to but only know the component the issue is relevant to.

Erin Fitzhenry_psvar6 · Answer

We have a similar use case. SMEs create tickets based on user-facing Compass components. Then, Jira automation routes the issues to the correct teams. Since I cannot extract the Owner Team from the Compass component, I have to (imperfectly) duplicate component-to-team mappings in automation. Creating a component is then a two-step process, first creating it in Compass and then updating Automation. If the PM forgets to update automation, the tickets are orphaned. I had to write a separate automation to report the orphaned tickets.

This is one of many day-to-day frictions that are causing my company to push back hard on using Jira. We hit obstacles along every path because the features aren't quite finished or fully integrated in the ways one would expect across modules.

Mike Bodé · Answer

I am looking to do the same thing, however there doesn't appear to be a way to set the team via the automation api. This is a deal breaker for using compass, as the whole point is to assign issues to a owning team so they can then assign to their team members. I might as well assign to the PM the issue, which nullifies alot of the compass value around team ownership. This seems like an obvious oversight. How can teams not be usable in the automation?

Ofir Assif · Answer

UPDATE

I've found that to see all possible fields available to use in an automation you can use the Atlassian API for an example issue. Can be seen here in the docs. After checking out a few issues, it seems the owner team is not available as part of the components details..