Can I create a Custom Label type field and change the name from "Labels", to something like "Customer Name"?
This is possible. There is a great post about the differences between labels and multi-select fields from @Sam Hall back in 2017 that work a read so I have copied it below:
Labels vs multi-selectIt really depends on what works best for your users, and how important it is that you have control over the values that people pick.If you have a limited set of values that won't change often, and you want to restrict what people can pick, then a multi-select custom field is suitable.In my personal opinion, selecting values in a multi-select is a bit fiddly for end user, especially if they want to select more than one value. The field also takes up quite a bit of screen space if you have lots of options.Note that you can add a custom field of type "labels", i.e. you don't have to use the generic system labels field. You can have a custom field called "Customers", which works using labels. I think the auto-complete input method used by a labels field like this is much nicer than multi-select.Of course, labels are designed to allow users can add whatever values/items they want, so if you need this to be restricted then a labels type field might not be the right choice.In practice, if you have a clearly named labels custom field, you might find the creation of unwanted labels (mis-spellings, upper/lowercase differences) is rare, because the auto-complete functionality in labels naturally helps users pick the right values. If you are prepared to put in a bit of effort to guide users to pick the values you want, rather than creating new ones, it can work OK. You can also use filters to monitor and cleanse data to keep things tidy. Depends on the scale of use.As an aside, there is an open feature request for the auto-complete 'renderer' (i.e. the labels style interface) to be available for multi-select fields. In the comments on the issue, there is mention of this being available as a 'dark feature' for JIRA server (see the issue comments for details):https://jira.atlassian.com/browse/JRA-23013
Labels vs multi-select
It really depends on what works best for your users, and how important it is that you have control over the values that people pick.
If you have a limited set of values that won't change often, and you want to restrict what people can pick, then a multi-select custom field is suitable.
In my personal opinion, selecting values in a multi-select is a bit fiddly for end user, especially if they want to select more than one value. The field also takes up quite a bit of screen space if you have lots of options.
Note that you can add a custom field of type "labels", i.e. you don't have to use the generic system labels field. You can have a custom field called "Customers", which works using labels. I think the auto-complete input method used by a labels field like this is much nicer than multi-select.
Of course, labels are designed to allow users can add whatever values/items they want, so if you need this to be restricted then a labels type field might not be the right choice.
In practice, if you have a clearly named labels custom field, you might find the creation of unwanted labels (mis-spellings, upper/lowercase differences) is rare, because the auto-complete functionality in labels naturally helps users pick the right values. If you are prepared to put in a bit of effort to guide users to pick the values you want, rather than creating new ones, it can work OK. You can also use filters to monitor and cleanse data to keep things tidy. Depends on the scale of use.
As an aside, there is an open feature request for the auto-complete 'renderer' (i.e. the labels style interface) to be available for multi-select fields. In the comments on the issue, there is mention of this being available as a 'dark feature' for JIRA server (see the issue comments for details):
https://jira.atlassian.com/browse/JRA-23013
Hello @LazMay
Thank you for reaching out.
In fact, Jira Cloud application has an inbuilt custom field of the type "label", which works exactly as the system label field, however, you can change its name as you need.
P.S: Note that this field type is only available for Classic projects. For Next-gen projects, we're still working to implement that field type (see JSWCLOUD-18544)
Follow the steps below to properly create the custom field and check if it fulfills your need:
For more details about this custom field type or any other, you can check the documentation below:
Custom fields types in classic projects
Let us know if you have any questions.
Thanks for your quick response. What does this mean? "You can have a custom field called "Customers", which works using labels"
Thank you @Petter Gonçalves for your reply. One last question, Can I use REST API (Json) to update this Custom label field? Would you have a code example?
Hi @LazMay
Im having the same issue at the moment. i need to link User stories & Epics to customers. how did you solved this issue?
Thanks
It looks like you're new here. Sign in or register to get started.
