Escaping spaces when setting issue fields using automation

[Andrew Berry]

I've created a custom labels field called "Issue context". What I'd like to do is combine several fields into that context field when an issue is edited, including:

1. Two single-valued custom fields

2. The issue components

3. Any labels

I have a basic automations set up, but it's creating entries with spaces as if they are multiple labels.

When I use smart values such as:

{{issue.customfield_10117.value}}

I'll get one label set per word.

Escaping it with:

{{issue.customfield_10117.value.asJsonString}}

Still gives me one label set per word, but with quotes :

Any ideas?

[John Funk]

Hi Andrew,

I don't think I have answers for you for getting rid of the quote marks, but I am curious what you are actually trying to accomplish. Maybe there is another route to go. 

[Andrew Berry]

We're taking several common labels and turning them into dedicated fields or components. However, we've now hit more fields than are allowed to be rendered on the kanban board, so I was hoping to join them all into a single field for display there.

[John Funk]

Take a look at this article and see if the combining of fields section helps:

https://support.atlassian.com/jira-software-cloud/docs/smart-values-lists/

[Andrew Berry]

It looks like either the docs or the app have a bug. Pasting in the example call to join the fixVersions field isn't accepted.

{{issue.fixVersions.name.join(" - ")}}

Typing it in by hand doesn't work either, because as soon as I press the space bar it closes the smart value. 

[John Funk]

You should probably go ahead and submit a Support Request to Atlassian then. If you don't mind, post back here what the solution was so we can close it out. :-)

[Andrew Berry]

Support reminded me that labels can never have spaces in them, which is why this wasn't working. Switching to a plain text field fixes this. Thanks for the suggestions!

[John Funk]

Great - glad you were able to get to a solution. :-)