[Bug] jira-search is broken since Atlassian deprecated corresponding API

[mitch0667]

Describe the bug
Single Jira item can still be retrieved successfully but jira-search blocks are returning HTTP error 410.
Information about Jira API deprecation:
https://developer.atlassian.com/changelog/#CHANGE-2046

To Reproduce
Steps to reproduce the behavior:

1. Create some jira-search block, with any jql
2. See HTTP error 410

Expected behavior

• Update codebase to migrate to supported Jira API
• have jira-search returning list of Jira items instead of HTTP error 410

Screenshots
If applicable, add screenshots to help explain your problem.

Plugin version and platform
I noticed it on 1.57.0 Windows app but due to root cause, all versions and OS must be impacted

• Version: 1.57.0
• Obsidian Windows
• Obsidian Mac
• Obsidian Linux
• Obsidian Android
• Obsidian iOS

[mitch0667]

Thanks for this great plugin!
I can help fixing the issue if it helps.
Actually I have already started
I may complete it by tomorrow and I can then raise PR, once tested.

[EnglishLFC]

I have the same problem on Mac OS Sequoia 15.6.1. (OS doesn't really matter since they've changed the endpoint)

After investigating this problem, seems that a GET request using a browser (Safari for me) with the same queries, is successful. Doesn't appear that any redirects are happening either.

Use a query in the browser: Ok
Use same query in Obsidian: HTTP 410

[kbcmdba]

Some help from ChatGPT...

Absolutely — here’s the generic version of the Obsidian Jira plugin patch to support Atlassian’s new POST /rest/api/3/search/jql endpoint, with all company-specific JQL removed.

---

🛠️ Purpose of Patch

This patch updates your Obsidian Jira plugin to comply with Atlassian’s August 2025 deprecation, which removed the legacy:

GET /rest/api/3/search?jql=...

You must now use:

POST /rest/api/3/search/jql

---

✅ Plugin Code Patch

Find the part of your plugin where it makes the Jira query (typically in jira.ts, api.ts, or a similar module).

🔄 Replace this 

GET

 call:

const response = await fetch(
  `${this.baseUrl}/rest/api/3/search?jql=${encodeURIComponent(jql)}&maxResults=50`,
  {
    method: 'GET',
    headers: {
      'Authorization': `Basic ${btoa(this.email + ':' + this.apiToken)}`,
      'Accept': 'application/json',
    },
  }
);

---

✅ With this 

POST

 call:

const response = await fetch(`${this.baseUrl}/rest/api/3/search/jql`, {
  method: 'POST',
  headers: {
    'Authorization': `Basic ${btoa(this.email + ':' + this.apiToken)}`,
    'Accept': 'application/json',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    query: jql,
    maxResults: 50, // optional: make configurable
    fields: ['summary', 'key', 'status', 'issuetype', 'created'], // optional: reduce payload
  }),
});

---

📁 File Location and Deployment

• If using a community plugin: modify and rebuild the .ts file (use npm run build)

• If using a precompiled version in .obsidian/plugins/PLUGIN_NAME/: you can modify the .js file directly as a quick fix

After editing:

• Restart Obsidian

• Test your JQL blocks again

---

✅ JQL Example for Testing (generic)

Inside your .md file in Obsidian, try something like:

jql: created >= startOfDay() AND issuetype IS NOT EMPTY

Once patched, this should return issues correctly using the new API.

---

✅ Summary

Step	Description
🔄 Replace GET /search?jql=...	Must now use POST /search/jql
📦 JSON Body	{ query: ..., maxResults: ..., fields: [...] }
⚙️ Fields	Optional, but helps reduce payload
🧪 Test	Use generic, bounded JQL like issuetype IS NOT EMPTY AND created >= startOfDay()

---

Would you like me to:

• Generate a ready-to-drop .js patch file?

• Help add plugin UI support for setting maxResults or field filtering?

• Turn this into a GitHub PR if you’re maintaining a forked plugin?

Let me know!

Absolutely — here’s the generic version of the Obsidian Jira plugin patch to support Atlassian’s new POST /rest/api/3/search/jql endpoint, with all company-specific JQL removed.

⸻

🛠️ Purpose of Patch

This patch updates your Obsidian Jira plugin to comply with Atlassian’s August 2025 deprecation, which removed the legacy:

GET /rest/api/3/search?jql=...

You must now use:

POST /rest/api/3/search/jql

⸻

✅ Plugin Code Patch

Find the part of your plugin where it makes the Jira query (typically in jira.ts, api.ts, or a similar module).

🔄 Replace this GET call:

const response = await fetch(
${this.baseUrl}/rest/api/3/search?jql=${encodeURIComponent(jql)}&maxResults=50,
{
method: 'GET',
headers: {
'Authorization': Basic ${btoa(this.email + ':' + this.apiToken)},
'Accept': 'application/json',
},
}
);

⸻

✅ With this POST call:

const response = await fetch(${this.baseUrl}/rest/api/3/search/jql, {
method: 'POST',
headers: {
'Authorization': Basic ${btoa(this.email + ':' + this.apiToken)},
'Accept': 'application/json',
'Content-Type': 'application/json',
},
body: JSON.stringify({
query: jql,
maxResults: 50, // optional: make configurable
fields: ['summary', 'key', 'status', 'issuetype', 'created'], // optional: reduce payload
}),
});

⸻

📁 File Location and Deployment
• If using a community plugin: modify and rebuild the .ts file (use npm run build)
• If using a precompiled version in .obsidian/plugins/PLUGIN_NAME/: you can modify the .js file directly as a quick fix

After editing:
• Restart Obsidian
• Test your JQL blocks again

⸻

✅ JQL Example for Testing (generic)

Inside your .md file in Obsidian, try something like:

jql: created >= startOfDay() AND issuetype IS NOT EMPTY

Once patched, this should return issues correctly using the new API.

⸻

✅ Summary

Step Description
🔄 Replace GET /search?jql=... Must now use POST /search/jql
📦 JSON Body { query: ..., maxResults: ..., fields: [...] }
⚙️ Fields Optional, but helps reduce payload
🧪 Test Use generic, bounded JQL like issuetype IS NOT EMPTY AND created >= startOfDay()

[kbcmdba]

I love the Jira plugin and continue to use it in spite of not being able to get my dashboards right now. I am able to get single issues without problems, so it's still at least minimally useful. 👍

[mitch0667]

@doteloenguin already rose some PR with a fix:
#175
I successfully tested it on my side.
@marc0l92 , is there anything I can do to help including this fix in new plugin version?

[intothegarden]

Is this going to be included? Currently the plugin is totally broken for me (and presumably for everyone else to)?

[jgdovin]

I love the Jira plugin and continue to use it in spite of not being able to get my dashboards right now. I am able to get single issues without problems, so it's still at least minimally useful. 👍

really bad form to dump a massive AI generated response. Does it even work? I'm guessing no since you say you can only get single issues still. Please delete your post and refrain from this in the future across all repositories.

[Dihgg]

Hi, just to update here, Seems like the plugin is working again. I am able to get my dashboards once more!

[EnglishLFC]

All good here, I wrote some Python to achieve the same results until I could update to the new version.

Works well, thanks for the quick response.

[matchavez]

I was just frustrated the switch was hidden in the user account. Didn't find it until I went to test the connection.