Use labels for Service Catalog item Custom Fields

This would be a fantastic and much needed upgrade!

Yes please.

what does open for consideration mean?

Here’s a visual justification of why requester-facing labels would be ideal. This isn’t an ordered list, but has to be presented that way because the names have to be unique:

I agree on the request. I could make use of another field as well that is filled with search terms.

One person searches for “laptop”, “notebook” or “pc”. And the service request is only called “Order new computer”. And noone finds this with their search. I dont want to fill every synonym into the description.

Only the short description and the name of service requests is searched through.

Hello @afautley - ‘Open for Consideration’ means that the feature request is currently being reviewed and considered by the product team and a final decision is yet to be made whether it will be included in the roadmap or no. 

For any more details, please refer to our Product Ideas FAQs : 

Thanks Alyssia

FYI

@BrynCYDEF  @msconfig87 @zachary.king @Daniel Söderlund @eeha0120 

Thats good to know. I wonder what the review cycle time is.

at least 8 months. 🤣

@mbackwater42 🌦 - we didn’t get an update yet 🙈. I’ve just checked in with the team, let me circle back if there’s been any more info on this request.

I’m facing this issue now. I have a dropdown with 3 dynamic sections that result and I want an “Additional information” field for all 3 of them, but the field name “Additional Information” is already taken.

Creating a shared filed for this seems silly as a workaround. 

​@Kenth  at the moment I simply use the dropdown value in the name as well. like “Additional information Option 1“, “Additional information Option 2“, “Additional information Option 3“

I had the same issue with some service items. With dropdowns, it’s not too bad because you can create a copy of the field, but unfortunately, that’s not always possible, and suddenly the field names start getting stranger and stranger.