Filter API returns HTTP 405 error on Jira Server but not on Jira Cloud

Question

I'm sure this has been asked before, but I can't seem to find a reference to it.

If you do

GET /rest/api/2/filter

on Jira Cloud, you get back a list of all known filters; however, if you do the exact same

GET /rest/api/2/filter

on Jira Server, you get a 405.

Does anyone know why there is a difference?

Daniel Vacanti · Answer

Hi Thomas,

Thanks for sharing your thoughts.  Unfortunately, though, my question hasn't been answered.  But that's ok.  I was just looking for some more transparency around what things are different between the cloud and server apis and it seems that doesn't exist.  Some justification why certain apis are implemented differently would be nice to have.

Thanks,

Dan

Thomas Deiler_db00h3 · Answer

Dear @Daniel Vacanti,

was your question meanwhile answered?

So long

Thomas

Thomas Deiler_db00h3 · Answer

Dear @Daniel Vacanti,

I'm not an Atlassian member - best you ask exactly your question one of their product managers.

There are even more differences between Cloud ans Server. For example, some JQL functions are only available for Cloud, but for Server you have to use a 3rd party plugin.

I guess, when you are searching at https://jira.atlassian.com for suggestions with this subject, you will find some.

So long

Thomas