You’re offline. This is a read only version of the page.
The "When a new issue is returned by a JQL query (V2)" trigger provided by the official Jira connector always results in an 400 error. The error message is as follows:
Share
ReportX-Request-JiraInstance is not provided
This is despite the fact that I've provided my instance:
A glance at the flow checker reveals that the URL does, in fact, get replaced by a 32-digit code, and is included in the request:
The only thing out of place, as far as I could tell, was that the header in the request is called "X-Request-Jirainstance", and not "X-Request-JiraInstance". Is this the problem? If so, where could I report this, and what would be the workaround?
Hello @co1 , your fix works for me too... awesome!
Hi! Thanks for keeping us updated on this issue. So far I'm having the same issue than Mario. I set up a new Connection and a new Flow. Set up the When a new issue is created (V2) and add the URL as a Custom Value. After that, it populates the list of Projects (meaning the URL is OK, because if it wasn't it wouldn't show the list of actual projects)
After a test tho, I get an error "Expression value is invalid. Value is not a valid absolute URL." I've tried inserting the URL in multiple ways, but with no luck.
If anyone has any ideas on what could be the issue would be great. Thanks in advance!
PS: I opened a ticket with MS for this issue, seeing I'm not the only one experiencing it. If I get any response I'll update here or create a new Topic so I don't hijack this thread.
For me, the Jira Instance doesn't automatically appear for selection. To resolve this issue, I simply re-added the connector, and I switch between the two of them each time I add a trigger. This action then displays my Jira instance, although in the incorrect order with the instance listed below the project. However, once displayed, it shows all our Jira projects, allowing me to choose the one I need. I hope this explanation helps.
Thank you, Nakata, but even when I include the project path, I still have the same error. However, maybe I'm getting off-topic in the post, so don't worry, I'll continue running some tests. In the meantime, thanks for your support.
But this is no longer the bug it seem that there is some issue with the Project ID:
blblblbla.atlassian.net/jira/software/c/projects/XXX/
For me I added the project as custom value XXX and also would be carefull with the naming of the Project i am not 100% sure if an space is not an issue here in the screenshot the project name seems to be different in both screenshots... Not sure but pretty sure this is not the stupid bug which triggered the initial post.
Hello Nakata, this is the test flow (quite silly), as you can see, it still generates an error (though it's no longer a connection error, but I think it's similar). It's strange that the trigger parameters request the project first and then the instance. Of course, if you don't enter the instance first, you won't find any project. I'm probably doing something wrong...
1. make sure you use the v2 (preview)
2. Make sure that you have a new flow, it seems updateing old ones is somewhat limited or simply not working.
Works for me now i am just missing a connector which is actually checking for updates on issues 😄 i guess a 12 hour loop and sync of all data is the way to go ..
#1
DBO_DV
25
Super User 2025 Season 1
#2
CU09051456-0
22
#3
Michael E. Gernaey
10
Super User 2025 Season 1
All responses (
Answers (