Hi, I want to create a custom field for my project, which lets the user insert as many URLs (or strings, for that matter) as they would like, with no predefined set of options as given by the multi select list custom field. The best compromises I thought of are: * Using the rich text custom fields, and separating each URL with a newline character. This feels like a hard-to-validate and inconvenient way of solving this. * Using the labels custom field, but this means that countless of labels will be created and stored. This also means that the user would have to create a label each time when updating an issue. I really think this could be a useful custom field, and I would love to have it by default :)

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

List Custom Field with Arbitrary Values

hagai.wechsler

Hi,

I want to create a custom field for my project, which lets the user insert as many URLs (or strings, for that matter) as they would like, with no predefined set of options as given by the multi select list custom field.

The best compromises I thought of are:

Using the rich text custom fields, and separating each URL with a newline character. This feels like a hard-to-validate and inconvenient way of solving this.
Using the labels custom field, but this means that countless of labels will be created and stored. This also means that the user would have to create a label each time when updating an issue.

I really think this could be a useful custom field, and I would love to have it by default

Accepted answers

Oliver Siebenmarck {Polymetis Apps}

Hi @hagai.wechsler ,

Welcome to the community!

There is an URL custom field type, but of course that's only a single URL.

I don't think the label-based option will work well, as you'll likely want the URLs to be clickable links.

The rich text field will likely be the best approach, although I agree that it is not easy to validate. Still possible, but you'll need some kind of Jira Expression based Validator App for your Workflow (in my biased opinion Cloud Workflows is a great choice, but there are many others).

Having said all that, I would actually recommend looking into building your own custom field using Atlassian's Forge platform. While there is some development effort, it should be rather straight forward to build and deploy a custom solution for your team. Especially, if you already have in-house technical knowledge. If you want to go that route, I'd start here:

Hope that helps,
Oliver

All comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

You need to decide if you want a field that can accept new values from the user or not. Label are ideal for what you describe for the end-user, but you then say that you want to limit what they can put into the field. Which is it?

hagai.wechsler

My use case is to have a field which is a list of Github commit links. I want the user, per issue, to insert the related commits.

I don't want to limit what they can put into the field, but only to validate that they are in a given format. In this case - a URL.

Oliver Siebenmarck {Polymetis Apps}

Hi @hagai.wechsler ,

Welcome to the community!

There is an URL custom field type, but of course that's only a single URL.

I don't think the label-based option will work well, as you'll likely want the URLs to be clickable links.

Hope that helps,
Oliver

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud