@huwshimi
> (you might click on "Huw Wilkins" and the input is populated with "huwshimi").
We do show the Lp-id in the picker, so the user is picking the huwshimi text.
I put some thought to this. I think the ideal scenario would be to show the same user/object presentation in the form:
Assignee: @Huw Wilkin (huwshimi) (/)
The real field is hidden; it still gets the Lp-Id that the current UI shows.
For an empty field I would see:
Assignee: None (/)
Making the input field hidden for a picker is simple, maybe a few lines of code. I do not know what we show in the page where the field was, and I cannot judge the effort to show formatted values for picker choices in a form. Maybe this is a simple as setting the title of the term (the value converted to a term) to the desired markup instead of using the Lp-id. I cannot say this is in scope. Have users reported that they do not connect the Lp-id in the picker to the Lp-id in the field?
@huwshimi
> (you might click on "Huw Wilkins" and the input is populated with "huwshimi").
We do show the Lp-id in the picker, so the user is picking the huwshimi text.
I put some thought to this. I think the ideal scenario would be to show the same user/object presentation in the form:
Assignee: @Huw Wilkin (huwshimi) (/)
The real field is hidden; it still gets the Lp-Id that the current UI shows.
For an empty field I would see:
Assignee: None (/)
Making the input field hidden for a picker is simple, maybe a few lines of code. I do not know what we show in the page where the field was, and I cannot judge the effort to show formatted values for picker choices in a form. Maybe this is a simple as setting the title of the term (the value converted to a term) to the desired markup instead of using the Lp-id. I cannot say this is in scope. Have users reported that they do not connect the Lp-id in the picker to the Lp-id in the field?