Confluence jira issue macro uses space to separate multiple values, why?

[Barry Kaplan]

In a filter within jira, a multiple value field will show the values comma separated. But when using the confluence jira macro that multiple value field will shows the values separated with spaces. 

This seems like a bug. Especially for the case when the field values themselves contain spaces.

[AnnWorley]

Hi Barry,

Please help me understand where you are seeing the space-separated values in Confluence. Perhaps it would help if you post a screen shot.

Here is a sample of a Jira filter in Jira and Confluence. The multi value field is "project" and it uses a comma in both Jira and Confluence. When I removed the comma in Confluence I got a JQL syntax error.

Jira:

Confluence:

Thanks,

Ann

[Barry Kaplan]

Ann, I am not referring to the query, but to the rendered output of the macro.

I can't show it in the edit view, because that view is not scrollable to see all the columns. But in the screenshot below the "Employee Roles" field is a "Select List (multiple choices)" custom field. The values "CISO" and "Employee" are two values assigned to the field for the issues. As you can see the values are separated by space.

In Confluence: 

But in the filter view they are separated by commas.

In Jira:

[AnnWorley]

I am seeing the same behavior on my test instance so I opened a bug report for the development team: Jira Issues Macro displays multi-select custom fields separated by spaces

Please comment or vote on the bug report to communicate directly with the dev team and add weight to your use case.

[Barry Kaplan]

That issue is for server. I am on cloud.

(The issue did not let me make any edits or even comments)

[AnnWorley]

You have to be logged into the bug tracker to make comments or vote, etc. I opened the same bug report for the Cloud project since you are seeing the behavior there as well: Jira Issues Macro displays multi-select custom fields separated by spaces 

I am sorry I did not notice which platform you were on but apparently, the issue is present in both. Thanks for pointing it out.