Hello
There is bug in the integration,
Sometimes tickets fail creating with Unauthorized error from jira
It seems the intercom is using a wrong/expired header token while sending request to jira
I attached here the screenshots
Best answer by bernice
View original
+4
I'm asking because if you check out Jira's status page they have a few alerts from the 4th - 7th that mention problems creating issues.
I'm wondering if that could be related to what you are seeing?
Its been a month there
since we started using workflows and jira integeration
+4
Hey
Hi, I’m having this same issue.
It seems like when you install the app (Jira for Tickets on Intercom) for the first time it works fine but eventually the token expires and it is never refreshed.
+3
Hey
I see that you were in contact with my teammate Sara. How did it go with that?
Are you still experiencing the same issue? If so, please feel free to reply to us in the same conversation you have with Sara.
Thanks!
Hi there - We also experienced the same issue when we installed the Jira for Tickets app. Jira issues would be successfully created and then suddenly, they wouldn’t and we’d see that 3rd party authorization error. Is there any sort of timeline for when this bug will be looked at? My team has had to pause using this app, as it created a lot of redundancy in ticketing process because the jira issue creation would fail and all they could do was create a new ticket and hope it worked.
+3
Hey
Checking the issue report, I see that it is still being worked on. I have just forwarded your message to the support engineering team, and you will receive an update via email from us when the issue is resolved.
Thanks!
Hey Ayk,
how about the status? We receive this error on a daily basis and it makes working with it a pain…
Best
Daniel
+3
Hey
I have just followed up with the product team regarding a status update on this issue now. You will hear back from our team when we receive any update via email.
We will also post here once this issue is resolved. 👍
We are having the same issue.
+3
Hey
Thanks again for reporting this issue! We have received an update from our product team, and it looks like they have fixed the issue.
Could you please check it on your end, and let us know how it goes? If you are still seeing new occurrences (from today) let us know, and I can check with them again.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
