Jira API migration for JQL based Trigger

(3) Share

Report

Posted on by dorlis

Hello,

I'm using "When a new issue is returned by a JQL query (V2)" as a trigger in some of my flows.

The trigger stopped working and I started getting a Flow Checker error with the message copied below:

The requested API has been removed. Please migrate to the /rest/api/3/search/jql API. A full migration guideline is available at https://developer.atlassian.com/changelog/#CHANGE-2046

It seems that the existing trigger targets a Jira endpoint which is now deprecated.

Is there any way around it with some modification in the existing JQL-based Trigger? Is there maybe some new Jira-specific trigger (say, "(V3)") being prepared for this? Are there any other meaningful options here beyond general HTTP hook based triggers?

Thank you in advance.

Dimitris

Categories:

Using flows

I have the same question (15)

All responses (7)

Answers (1)

Sort by

Suggested answer

Michael E. Gernaey 53,963 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

@dorlis

This unfortunately not a Microsoft adapter connector, you would need to go to Atlassian and ask.

Looking at the connector I do not see that its changed.

however, did you go to the link above, and verify the new URl they want you to use, from the link you have above

https://learn.microsoft.com/en-us/connectors/jira/

If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

Thank you!
Sincerely, Michael Gernaey

If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

Thank you!
Sincerely, Michael Gernaey

Was this reply helpful? Yes No
SS-03090353-0 3 on at

Like
a
(0)

Report
Copy link

Link copied!

Same problem here.

Was this reply helpful? Yes No
jawilson 13 on at

Like
a
(0)

Report
Copy link

Link copied!

I've the same issue here. I have had to create a work around using a different trigger but this means I'm losing out on extracting some of the field data from the Jira work item which I was using in my Flow. Interestingly the reply from Atlassian is that I need to contact Microsoft as the Power Automate connectors are theirs!

Was this reply helpful? Yes No
WW-04092201-0 5 on at

Like
a
(1)

Report
Copy link

Link copied!

@Michael E. Gernaey this page states that the Jira integration is managed and published by Microsoft:
https://learn.microsoft.com/en-us/connectors/jira/

1 people found this reply helpful.

Was this reply helpful? Yes No
ND-08090642-0 4 on at

Like
a
(1)

Report
Copy link

Link copied!

Atlassian changed their API, announced it in 2024. The Jira integration in Power Automate is created and maintained by Microsoft, therefore it is Microsoft's responsibility to update their product to the new API.

Instead of pointing fingers to Atlassian (that can't do anything since it is not their integration product, see Solved: Use New API 3 in Microsoft Power Automate JQL trig...), can someone from MS have a look at this and this it, I bet it is a 1 man-day fix.

Tx

1 people found this reply helpful.

Was this reply helpful? Yes No
Verified answer

dorlis 30 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi all,

Just stating that the trigger must have been properly updated a few days ago as existing flows started running smoothly again.

For what is worth and in case it helps anyone track the missed triggers, the down time seems to have been from early on September 2nd to early September 11th.

Was this reply helpful? Yes No
dorlis 30 on at

Like
a
(0)

Report
Copy link

Link copied!

Apparently this broke down (again), initially with insufficient parameters (see Adding Query Parameters in Trigger (JIRA JQL)) and now back to being completely untriggered.

Any ideas or comments anybody?

I'm still hoping I'd be avoiding building webhooks...

Was this reply helpful? Yes No