Our confluence pages have a jira issue filters on them. This filter is set to show us four fields: Key, Summary, Status and Confluence Page. Confluence Page is a custom field we have created in Jira - free text. Previously these macros all worked correctly and all fields showed the correct values.
Recently (we are on Confluence Cloud and have not manually updated or changed anything on our system ourselves), the macros have stopped showing the Confluence Page value in our filters. I can see the value is still on the issue itself.
The xml export of the issue shows the custom field exists and has a value attached. I have tried removing the macro and replacing it. I have checked the custom field itself and it has a global context.
A different Custom Field (project extension) was added (for testing purposes) and I can see the value of that field in my macro. This custom field is not free text but rather a list selection. Looking at the xml for these two custom fields, the only difference between the two is that the Project Extension field has "key="10501" as part of the customfieldvalue itself. The Confluence Page field does not have a key.
Does anyone know why the free text custom field is no longer showing in the macro and the list selection one is? Is there something else that I have missed that might explain why my Confluence Page field is no longer showing? Or has this broken as part of a Cloud system upgrade? If so, is it on the radar to be fixed? Whilst not a massive issue - it is something that needs to be fixed for us. I have looked at (issue) but that is closed and my problem is still happening. Maybe not fixed for cloud users?
Also having (and ignoring) this issue since 2 months.
So apparently there was a fix for Confluence Server.
For Confluence Cloud when browsing then these bugs (and maybe more) seem to point to the same issue
A very similar problem here... A confluence page using a Jira filter containing custom fields all of a sudden (last week...?) does not display any values. In the sample picture, "external release notes" would normally show a text (which can be found on the Jira issue itself).
A theory to my reported problem here: seems related to custom fields with overlapping names from JIRA next-gen projects. This apparently makes the system mix things up. In our case, after finding and removing the next-gen fields, and waiting over night (sync delay jira - confluence?) the original pages in Confluence with Jira filter pages started to work again, and displaying the custom field content correctly.
Hi, Confluence collaborators! As part of #Confluence-Collaboratory month, we’ve created a very special Mythsbusters segment, where we're dive into an interesting myth and uncover the truth behind i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events