Just tried this in Jira / Confluence cloud and it seems to still be broken - see image below:

Looks great, thank you.

Ya, sure ialexeyenko.

Hey psuwala.

Thank you for addressing the bug! It seems that fix version 7.12 was confused with 7.12.0 (the later ha already been released).

Could you please update the bug, i.e.:

• set the proper fix version
• transition issue to the correspondent status
• drop the 7.12 version to avoid further confusion ?

Thank you!

Cheers,
Ignat Alexeyenko
Jira bugmaster.

Nareszcie  

Hello,

Sorry for your wait.
From now on I will take care of this bug.

Stay tuned.

hello 

please any update about this issue ? 

in which version it has been fixed ? 

is there a workaround for this?

any update on this? it appears to have been around for 5 years, is it that big of a change to make?

I think what is missing is a clear description of what the XML Export feature is intended for.

Guess this issue also impacts, that a JIRA query in Confluence shows (in table view) the internal ID of a multi version picker field instead of the value.

Would also appreciate, if this gets fixed as also with my clients this is an issue in reporting.

Thanks!

Wolfgang

Guys, is there any progress with this issue? It's from 2013 for God's sake....!

Is this going to be fixed anytime soon? Is there any workaround?

Dears,

  This is far from being reasonable! I'm currently in the process of showing in the E.Commission why we chose the Atlassian suite instead of continuing with IBM stack. One of the things is about reporting and Dashboards! I have a few custom fields and they are displayed as number! How am I expected to be able to do this if for instance, in a Programme dashboard, instead of having the team's name, I have a number.

  Please, sort this ASAP, as it's coming since years ago!

Many thanks!

Tiago Palhoto

Hi,

we have the same Problem with the following Versions:

• JIRA (v7.3.1)
• Confluence 6.1.2

When will this issue be solved?

Hi,

Same problem here, fixing this problem would be highly appreciated by our developpers.

Regards,

Romain

Hi,

Please fix it quickly. I will be waiting for it to be fixed.

Thanks.

Hi all, 

a fix of this issue would be appreciated very much! Could you let us know, when you plan to fix this?

Thx, Manuel

Hi,

When will this issue will be handled ?? it's been reported at 2013(!!)

Many thanks.

Could you please let us (the users!) know if you plan to fix this at some stage?...Many thanks!.

Please fix this AS SOON AS POSSIBLE!!!

We are trying to leverage Confluence for status reporting with JIRA data being the source of truth, however with our custom fields not displaying properly, we don't have all the information needed.  We want to avoid creating data that only lives in Confluence and not in JIRA. 

We're trying to use Confluence to automatically generate test reports using JIRA data.  This bug is preventing us from providing 'bug will be fixed in version x' data, so a blocker.  Please fix ASAP!

Good Day,

I just wanted to raise awareness again for this Bug since it still seems to be present.
We are heavly relying on features like this to work and don't really want to add third party plugins or nasty workarounds if there is a built-in way of handling these issue.

Hope you'll guys put this on the Agenda for it seems it should be only a quick fix.

Thanks.

André

This is something not working, so the priority should be Major - Blocker is reserved for problems on the level of being completely unable to use JIRA.

Switching priority to blocker as this is preventing the macro in wiki from working properly impact the development process.