-
Type:
Suggestion
-
Resolution: Low Engagement
-
Component/s: Assets - Service, performance, functionality
-
2
Problem
Currently only text type attribute are eligible as Label attributes in an object type as per Set the label of an object type
Suggested Solution
Allow non-text attributes to be made Label attributes
Why This Is Important
The below use case explains the purpose clearly:
Imagine an object which represents a jira user. At this moment you need to have text-type attribute with "label" property, as well as user-type attribute with the selected jira user. Problem is that text-type field in this case is redundant as you have everything in user-type field, and it would be perfect to have only this user-type field, and not copy manually user name into text-type field because it is the one which can be set as "label". Any case where non-text-type field represents a core object value will apply to this improvement, as it will narrow fields count to the minimum and saves manual filling of text-type field.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available