Insight Import with label

[David]

More a feature request then seek for help but if anyone knows a workaround shout out.

In our system our back end users who use Insight like to see a pretty label which I can appreciate as not everyone remembers IDs and associated them with users and assets. So we have made our label the display name for users which has a nice look. Here is the issue now whenever we wish to do an import insight for some reason requires that you also import a field in to the label which to me is absurd as a label can be anything and is not a unique identifier by any means across the system. So why do we need to include it in every single import?????

Apart from the nice look inside insight the label also affects the display of linked objects inside the attributes of another object which again serves no real importance apart from as the same suggests a label.

Atlassian can we remove the requirement to have the label in the import!

If any one knows a work around shout out please as this is a painful part of insight!

[Michael Cornel]

We faced exactly the same issue today. We are importing Slack channels, every channel has a unique ID that stays constant if the channel name changes. However we cannot use that ID since of course we want to have the name as the label, not the cryptic ID.

We have not found any workaround than to accept that changing a channel name leads to the creation of a new asset.