I have a problem with my Confluence page that displays JIRA tickets using a macro. Some tickets from my project keep showing a spinning loader that says “Getting issue details …” and it never stops loading.
I’ve already looked at the JIRA access logs and catalina.out files but there are no error messages showing up. I’m wondering if this could be related to permission issues or maybe something specific about those particular tickets like their fields, who they’re assigned to, or which component they belong to.
Has anyone else run into this issue before? Where else should I check to figure out what’s causing this problem? Any ideas would be really helpful.
had the same problem last month - it was a corrupted cache on confluence’s end. try clearing the macro cache or restarting confluence. also, check if those tickets have huge descriptions or lots of attachments. the macro can time out if there’s too much to load.
I’ve hit this exact problem before. It was custom field configurations on those tickets. The macro was trying to pull data from custom fields that got deleted or changed after the tickets were created, which caused the infinite loading loop. I checked the ticket schemas against working tickets and found the issue. Pull up your browser’s developer console while the macro loads - you’ll often see JavaScript errors that don’t appear in server logs but show what’s actually breaking. Also check if those problem tickets have attachments or comments from deactivated users. The macro sometimes can’t handle orphaned references and just hangs instead of dealing with missing data properly.
Check your JIRA-Confluence application linking config first. I ran into this same authentication timeout issue last year. The macro connects but can’t complete the handshake for certain tickets - usually ones with specific workflow states or security levels. Go to your Confluence admin settings and test the application link connection. If it’s working but slow, bump up the timeout values. Also make sure the service account for the integration has proper permissions to view those specific tickets. Sometimes tickets get moved between projects or have their security scheme changed, which breaks the macro’s ability to fetch them even though they look fine in JIRA directly. Since only some tickets are affected, it’s likely a permission or config mismatch rather than a general connectivity problem.