I have not had any problem with the up aside from the odd time where it no longer runs on the schedule, but a simple disconnect and re-connect resolves that.
I appreciate that Atlassian was able to see it's users need this. I hope we don't need to have this kind of reaction and instead to work with the customer base.
Thanks for not deprecating this feature - we find it very useful. If you'd like some feedback on how we think it can be improved, we'd be happy to provide it.
Thank you so much for this, now I do not have to worry where to get my regularly updated JIRA x googlesheet query. :( oh, of all the problems I encounter on a daily basis, this reverting of decision has given me more reason to live happily. :) Thank you!!! <3 <3
This is shocking... we are much dependent on this plug-in which helps us to build Low code products, analytics, etc
it will give us a big step back and months of reworking what we achieved through this so far...
I suggest rethinking from an end-user perspective.. might be uses of this low but the IMPACT IS SUPER HIGH but it just solves the high ambiguity problem simply by exporting data to sheets.
@1001- Beatriz Jiménez Pintre Atlassian reverted the original decision, therefore the app should work. If it doesn't, it a bug, not a planned stop of the app.
does anyone know how to resolve the problem? l am sure l only have one google account logged in my browser session, and the Jira clouds on other sheets seems refreshed normally, but only failed on this sheet
Only go into that with ONE account active. If you have two Google accounts going, it gets confused. Logout of all, login to the right one and you should be good.
still not work, l am sure there is only one account active and logged in. Not only me but also my teammates could not refresh the Jira Cloud in this sheet. However, the Jira Cloud on other Gsheets still work, l dont know what the root cause is and how to deal it actually.
All the google app script & IMPORTRANGE function on this sheet do not work....
173 comments