Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Custom JIRA field based on versions does not display correctly in Confluence

jllange
Contributor
November 28, 2018

I have a custom field in JIRA called "Planned Release" and it is a version picker.  When I try to display this column in confluence, I get a series of numbers, which I am guessing is the internal ID of the version, rather than the version name.

1 answer

1 accepted

0 votes
Answer accepted
Stephen Sifers
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 30, 2018

Hello Jennifer,

I was able to take your example and test through without issue. I tested on Jira 7.12.3 and Confluence 6.12. I created a custom field with a single select drop down and created it with 5 versions. From there I created a Confluence page with the Jira issue/filter macro and displayed the issues from my project. Here is what I am able to see within testing:

image.pngimage.pngimage.png

To further test, please let me know what version of Jira and Confluence you are actively using and I can attempt to re-create on those versions to see if there is a problem.

I look forward to your response so we may get this resolved and working for you!

Regards,
Stephen Sifers

jllange
Contributor
November 30, 2018

hi Stephen! Thank you so much for looking into this, here is what I see, the first in JIRA the second in confluence:

Screen Shot 2018-11-30 at 2.29.34 PM.png

 

Screen Shot 2018-11-30 at 2.30.15 PM.png

 

Confluence version 6.10.1 and JIRA version 7.12.0

Stephen Sifers
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 3, 2018

Hello Jennifer,

I attempted to recreate on the same versions you listed (Confluence 6.10.1 and Jira 7.12.0). I attempted to break the application links, recreate the application link and add additional custom fields. I was unable to recreate what you’re seeing on your end.

The good news is it seems there is a bug report with similarities to your current issue. You can find more for the bug report at CONFSERVER-43035. I will be linking this post to the bug report, we also suggest you vote and watch this to get future updates.

For the time being, there is not a current work around that is not disruptive. I have created a support request on your behalf for this issue as it may be something that may be resolved outside of an update. You should have an email shortly with the details of the support case.

Regards,
Stephen Sifers

Like jllange likes this
jllange
Contributor
December 3, 2018

Thank you!

Like Stephen Sifers likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events