-
Bug
-
Resolution: Unresolved
-
Low
-
4
-
Major
-
6
-
Issue Summary
The Jira Service Desk for Zapier app (maintained by the JSD Ecosystem team) polls the Jira issue search API to fetch issues to show Zapier users as samples.
This search also powers the Created Request and Updated Request triggers.
Because we fetch 100 issues at a time, if the issues are larger (and the combined response is > 6MB in size), Zapier fails to process the response.
Steps to Reproduce
- Create an account in Zapier
- Set up a rule with an Updated Request trigger
- Connect to a Jira site with at least 100 issues with a lot of data (attachments, fields, comments, change history, etc.) . such that the issue search returns > 6MB of data.
Expected Results
The samples are displayed to the user.
Actual Results
The user sees an error that the "body size is too long" and cannot continue to set up the rule with sample data.
Alternatively, if this were to happen when polling issues to trigger a rule the rule would fail to trigger and the user would be alerted by email.
Workaround
Currently there is no workaround.
- mentioned in
-
Page Failed to load
[JSDCLOUD-8652] Polling for issues to show sample issues, or perform the Created Request / Updated Request triggers sometimes fails if the issues are large
Hi this is blocking a lot of automation in my company! any updates on this or timelines to fix it?
I purchased zapier specifically for this capability, and my very first and only use case wont work due to this bug. Any updates?
Hi Atlassian Team,
This issue is completely blocking now important integration on which we spent some time building it via Zapier.
Do you have any timeline when you can fix it?
Maybe some workaround suggestion how to limit the payload size either from Jira or Zapier side?
Thanks,
Klime
Hi,
Do you happen to have a status or timeline or even if this is being addressed? We are trying to create an integration between Jira and Zendesk for a support customer and this bug is not allowing that to happen.
This issue is also affecting our abilities to bill correctly and our future expansion of our Jira footprint. Please escalate
Bill Bertolotti
Hi Team,
Can you please let us know when this issue will be resolved. We are suffering with this issue since our Zap's are not running that are integrated with Jira Service Management.
Thanks,
Venky.
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira Service Management Cloud users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know via raising a ticket at https://support.atlassian.com.
Thank you again for providing valuable feedback to our team!
Jira Service Management Cloud team
Any update? I switched from Zendesk to Jira and it was humming along just beautifully until bam, now one of my zaps won't work
We are suffering with this issue and as such our Zapier / Jira integration is unusable. Surely the simple fix is to reduce the search list of issues or make it configurable?
Hi Atlassian,
Jumping on this nearly 5 year old issue.
Have a use case to integrate with Monday.com because our sales team didn't like the Atlassian CRM offering. Blocked by this due to having no ability to keep monday items updated from Jira.
cd501002582e if you are still at Atlassian care to provide an update beyond what you supplied in May 2022?!? Informing people on a ticket which is designed to aid Atlassian in prioritising their backlog... that they should raise different support ticket in order to escalate seems to make this public facing Jira project a bit moot?
Based on my experience with timescales at Atlassian I will be recommending that Zapier IS NOT viable due to an issue Atlassian are procrastinating on.