Display of Jira filter in confluence doesn't work
Asked by NEGAR JALALIAN:

Hi this function was working before but suddenly I noticed that it stopped working .

the problem is : when in confluence I insert Jira filter as a table and among displayed fields , there is a custom field , I get this error :

Data cannot be retrieved due to an unexpected error.

[View these issues in Jira](https://jira.canaldigital.com/secure/IssueNavigator.jspa?reset=true&jqlQuery=filter%3D15310++++++&src=confmacro)

![confluence error.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/72848i396F95AECC41A16E/image-dimensions/504x124?v=v2 "confluence error.JPG")

but when I remove the custom field from display option , it works


Answers:
author: Luke Gartland
body: Hi all,   

My team and I are currently experiencing this issue as well. Our previously working 'Trending Issues' filter now says "Data cannot be retrieved due to an unexpected error" for our userbase. This is a **high-impact** outage so we're looking for a resolution ASAP.   

Has anyone found a workaround or fix in the absence of help from Atlassian?

comments: author: Moritz Wagner
body: Yeah in atlassian timelines this is a brand new bug that might be fixed within the next 20 Years, probably:

<https://jira.atlassian.com/browse/CONFSERVER-35196>

and

<https://jira.atlassian.com/browse/CONFSERVER-53500>

I'm pretty sure these two issues will be fixed atr once as they share most likely the same source. And as they are opened very recently in 2014 I guess they will be solved as soon as AI takes over all these problems in 2078 :)


author: David Vanek
body: Moritz, you've made my day:-)

BTW possible workaround, but not suitable for every use cases:

[https://marketplace.atlassian.com/apps/1217420/database-connector?hosting=server\&tab=overview](https://marketplace.atlassian.com/apps/1217420/database-connector?hosting=server&tab=overview)

or

[https://marketplace.atlassian.com/apps/1211703/play-sql-base?hosting=server\&tab=overview](https://marketplace.atlassian.com/apps/1211703/play-sql-base?hosting=server&tab=overview)

or

[https://marketplace.atlassian.com/apps/1213501/sql-jql-driver-transform-jql-into-sql?hosting=server\&tab=overview](https://marketplace.atlassian.com/apps/1213501/sql-jql-driver-transform-jql-into-sql?hosting=server&tab=overview)


author: Diego
body: Hey there, thanks for reaching out, [@NEGAR JALALIAN](/t5/user/viewprofilepage/user-id/752794) !

I feel how frustrating situations like this can be. Something works and then, suddenly stops. The issue that you are facing can have a few reasons to exist. Let me tell you about them:
> 1. *Confluence Jira issue macro version is older than 5.6.1*
> 2. *Your user Oauth token is corrupted*
> 3. *There is a problem in your application link between Jira and Confluence*

Let us start by exploring a few things, Negar. Here we go:

++**New page, new macro**++
> 1. *Create a new page in Confluence*
> 2. *Insert nothing but the Jira issues macro*
> 3. *Use the exact same filter as you used before*
> 4. *Publish the page*
> 5. *Check if the issue persists*

++**Another user, another chance**++
> 1. *Open confluence with another user (not the one that you normally use to access Confluence)*
> 2. *Make sure that the user has access to both the Confluence page and Jira filter*
> 3. *Access the same page with the problematic macro*
> 4. *Check if the issue is still present*

Here we have some documentation on the issue and also similar ones. Take a look:
> * ++**[\[Confluence Server\] Specific User is getting "Data cannot be retrieved due to an unexpected error" when using JIRA Issue Macro](https://confluence.atlassian.com/confkb/specific-user-is-getting-data-cannot-be-retrieved-due-to-an-unexpected-error-when-using-jira-issue-macro-838275039.html)**++
> * ++**[\[Confluence Server\] Unable to load JIRA Issues macro on some pages](https://confluence.atlassian.com/confkb/unable-to-load-jira-issues-macro-on-some-pages-747834697.html)**++
> * ++**[\[Confluence Server\] Timeouts in the JIRA Issues Macro or Highlighting Plugin](https://confluence.atlassian.com/confkb/timeouts-in-the-jira-issues-macro-or-highlighting-plugin-726108967.html)**++

Hopefully, this gives you some direction on how to solve this situation, Negar.

I would ++*love to have some background*++ in your instance. With this purpose, I have raised these questions:
> 1. *Which version of Confluence are you currently running?*
> 2. *Which version of Jira are you currently running?*
> 3. *Was there any kind of change applied to your instance, prior to this issue?*
> 4. *Is there any other user who is also affected by this issue?*

Looking forward to your reply.

comments: author: NEGAR JALALIAN
body: Hi Diego

unfortunately your answer didn't help .

my problem is any time in display mode , I add a custom field , the Jira filter doesn't show in confluence and I get this error :

Data cannot be retrieved due to an unexpected error.

[View these issues in Jira](https://jira.canaldigital.com/secure/IssueNavigator.jspa?reset=true&jqlQuery=filter%3D15212++&src=confmacro)

and as soon as I remove the custom field, it works.

my confluence version : 6.15.9

my Jira version : 8.4.1

*- Was there any kind of change applied to your instance, prior to this issue?* No

*- Is there any other user who is also affected by this issue? everyone*


author: David Vanek
body: Hi Diego,

in our environment (Confluence 6.13.4 + Jira Software 7.13.5) we have exact the same behavior as described by Negar. If I add a custom field to view, filter doesn't show. Moreover field Resolved, which is build-in, does this error too.

So Negar, you are not alone:-)

Regards,


author: Diego
body: Hey, thank you both for keeping this thread alive. After I received the reply to my initial answer, I found this report:
> * ++**[\[Confluence Server\] JIRA Issues macro fails with custom field](https://jira.atlassian.com/browse/CONFSERVER-53500)**++

Currently, the best course of action would be to ++*vote and watch this report.*++ Voting helps to increase the report visibility and watching keeps everyone up to date with anything posted there.

As I understand, when you use the "*Resolved* " field the issue is also present. Is that correct [@David Vanek](/t5/user/viewprofilepage/user-id/2725844) ? Are you able to replicate this [@NEGAR JALALIAN](/t5/user/viewprofilepage/user-id/752794) ?

Let us hear from you both!


author: David Vanek
body: Hi Diego,  

yes, when "*Resolved* " field is used, the error happens. Without "*Resolved*" field, the issue filter is on confluence page was shown without problems.

UPDATE: This is odd - I've found out, that this error occurs only with some filters, e.g. if filter is project=aaa filter than it is shown even with Resolved, Custom Fields etc. but with filter project=bbb not.

Regards,


author: David Vanek
body: BTW CONFSERVER-53500 was created 18/Sep/2017 and is still not fixed?!


Tags: confluence-server

jira

macro

server