Display of Jira filter in confluence doesn't work

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

 

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

 

Diego_88dj6o

Hey there, thanks for reaching out, @NEGAR JALALIAN !

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
• [Confluence Server] Unable to load JIRA Issues macro on some pages
• [Confluence Server] Timeouts in the JIRA Issues Macro or Highlighting Plugin

 

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.