<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D5KZ00001LBtuP0ATOkta Identity EngineWorkflowsAnswered2025-09-08T18:48:32.000Z2025-09-02T21:10:23.000Z2025-09-08T18:48:32.000Z

TylerA.02538 (Customer) asked a question.

September 2, 2025 at 9:10 PM
Okta Jira Workflow Card "Search Issues by JQL" not working

I've had this workflow working for months but up until a few days ago it just stopped. The culprit is the Jira card "Search Issues by JQL" refuses to work.

 

Things I have tried:

  1. Create a new API token and reauthorize
  2. Ensured permissions on the Jira side were set correctly for the user trying to search
  3. Tried "Custom API Action" with the endpoint "/rest/api/3/search"

 

Anytime I try to search it loads for a minute or so and then returns null. Wondering if anyone else has been experiencing issues similar to this.

 

Thanks!

  • 6 answers
  • 438 views

  • TimL.58332 (Workflows)

    @TylerA.02538 (Customer)​  --> This is a known issue and is being investigated by Engineering. Jira has an article posted here: https://developer.atlassian.com/changelog/#CHANGE-2046. If you click "More Details" it will provide the new endpoints. Please note, Jira does mention some behavior changes on their new endpoint. I recommend reading through those.

     

    Using Custom API Action (CAPIA) to the new end point(s) should be successful.

    Expand Post
    Selected as Best

  • User17157611498146715886 (Customer Support Online Community and Social Care)

    Hello @TylerA.02538 (Customer)​ , thank you for contacting Okta Community!

     

    This issue seems too complex to be addressed here. I recommend that you open a Support ticket (Customer Support Account ID number required) so one of our engineers can analyze it and provide in-depth troubleshooting. You could also provide more details in a ticket that shouldn’t be given here, as this is a public space.

    Please note that opening a support ticket is a feature available only to paid accounts. If you do not have a paid account, but are interested in upgrading, you can contact our Sales team. 

     

    Regards. 

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Just released: More Okta Community badges just added

    Expand Post

  • TimL.58332 (Workflows)

    @TylerA.02538 (Customer)​  --> This is a known issue and is being investigated by Engineering. Jira has an article posted here: https://developer.atlassian.com/changelog/#CHANGE-2046. If you click "More Details" it will provide the new endpoints. Please note, Jira does mention some behavior changes on their new endpoint. I recommend reading through those.

     

    Using Custom API Action (CAPIA) to the new end point(s) should be successful.

    Expand Post
    Selected as Best

    • TylerA.02538 (Customer)

      Yea using the JIra CAPIA and calling '/rest/api/3/search/jql' was the fix. Thanks for the response!

  • DiegoR.78637 (Customer)

    Tyler, do you know if this also applied for the Search Issues card? I think those 2 cards point to the same endpoint.

    • TylerA.02538 (Customer)

      Most likely yes, I experienced very similar issues when I tried to switch to that card.

  • TonyV.25270 (Customer)

    Honestly disappointed in Okta for this. I had reached out a couple months ago inquiring if Okta workflows was ready for the deprecation of the old jql endpoint and was told that it was. The catch was that I had to update all my jql search cards to a current version. I spent a week going through and updating all my workflows only to do it all over again with the work around and having to run failed jobs which took even more time. If I had did the work around from the start, I would have saved myself a lot of time.

    Expand Post
This question is closed.
Loading
Okta Jira Workflow Card "Search Issues by JQL" not working