Is there a way to update Affected Services from an Assets Schema?

[Owen Adams]

Our applications database lives in it's own schema as there is not enough data points within Services for the information we want to know about an application. How can we ensure data continuity between the application schema and affected services for things like responders, stakeholders and tier level. We want to leverage the incident and change management of JSM without having to maintain data in two places.

[Matteo Vecchiato]

Hi @Owen Adams ,

Thank you for your post. I would suggest to create a reference ( a link ) between your own custom object type and the standard Services, instead of duplicating or updating data.

Hope it helps

[Ash H_]

Hi Owen, 

I'm Ash from Appfire. 

This may or may not help (hopefully, it does!) it seems like you might benefit from using JMWE. 

Updating the "Affected Services" field based on an Assets schema is a common requirement for maintaining data continuity in Jira Service Management. Native Atlassian Automation can handle this by using a "Lookup objects" action to find the relevant services within your schema and then using an "Edit issue" action with a JSON payload to update the field. This typically involves mapping the service IDs from your Assets attribute to the "Affected services" field. However, native automation can sometimes hit execution limits in high-volume environments, and complex mapping between Assets objects and system fields can be tricky to configure using only the standard UI.

Jira Misc Workflow Extensions (JMWE) can help you automate this synchronization more robustly, especially if you need to handle complex data mapping or want to avoid native automation limits. With JMWE’s Event-based Actions, you can trigger a field update whenever an Assets object is selected or changed on an issue. Using its simplified scripting capabilities, you can write a post-function to fetch the specific service information from your Assets schema and precisely map it to the "Affected Services" field. This ensures that your service data remains synchronized in real-time without manual intervention, even for sophisticated use cases where a simple one-to-one mapping isn't enough.

Again, hope it helps, and wishing you a lovely day. 
Ash.