Problem

Post re-creating application link between Jira and Confluence, Jira chart macro on Confluence page displays below error instead of authenticate button. :

Error message : com.atlassian.sal.api.net.ResponseException: Could not parse json

Environment

Jira and Confluence DC Application links

Steps to Reproduce

• Create application link between Jira and Confluence DC
• Add Jira charts and Jira issues macro issues on a Confluence page
• Delete existing application links and recreate application link
• Access previously created Confluence page with Jira Chart and Jira issue macro.

Expected Results

Post recreating app links, we should get the Authenticate link for Oauth token regeneration like for Jira Issue Macro.

Actual Results

We could see  error message for Jira chart macro : com.atlassian.sal.api.net.ResponseException: Could not parse json message for Jira charts

Diagnosis

In Jira Iogs we could see HTTP 400 error code for the request : /jira/rest/api/2/search made from Confluence :

   172.50.0.2 o751x1662x1 - [15/Feb/2024:12:31:11 +0000] "GET https://linux-64066.prod.atl-cd.net/jira/rest/api/2/search HTTP/1.1" 400 152 0.0070 - "Apache-HttpClient/4.5.14 (Java/17.0.10)" -
        ___ Request _____________________________________________________
        Request URL Parameters : 
            jql=project in (KANBAN,SCRUM) order by updated DESC
            maxResults=0
    
            atlassian.core.seraph.original.url=/rest/api/2/search?jql=project+in+%28KANBAN%2CSCRUM%29+order+by+updated+DESC&maxResults=0

      
            
        Request Data (0 bytes).
        ___ Response ____________________________________________________
        Response HTTP Headers : 
            X-AUSERNAME=anonymous
            Cache-Control=no-cache, no-store, no-transform
            Content-Type=application/json
        Response Data (total 152 bytes) : 
    
    {"errorMessages":["The value 'KANBAN' does not exist for the field 'project'.","The value 'SCRUM' does not exist for the field 'project'."],"errors":{}}

Workaround

Edit the affected page 

Edit Jira chart macro

Login and approve and insert Jira chart macro-save the page.

Refresh the page, the exception will be gone and new Oauthe token is generated.

Note: This bug doesn't impact Confluence-Jira application links that are setup using authentication mechanism as OAuth(impersonation). The bug behaviour is noticed only when  authentication mechanism is OAuth