How to store multiple applications in one Jira Data Manager attribute

[Andrew Winter]

I am working with Jira Data Manager / Assets and need to associate more than one Application to a single logical record (for example, a service, component, or capability). I attempted to store multiple applications within a single attribute (for example, using comma-separated values), but Jira Data Manager treats this as one combined value rather than recognising each application separately. This causes issues with reporting, relationships, and data accuracy. I would like to understand: - Does Jira Data Manager support multi-valued attributes? - If not, what is the recommended modelling approach? - Should Applications be separate objects referenced multiple times? - Is a many-to-many (junction) object the expected solution? The goal is to follow Atlassian best practices, maintain normalized data, and support accurate reporting.

the example being a CSV file to Data Manager then we map from there and import it. we have an Application attribute but with One application against 1 server but we wish to account for more than 1 application without the Data Manager import failing and also the imports being able to match against our Application Object types in our Jira Schema.