Does Google Sheets import work at all?
Error sugegst that Import script sends invalid range command.
Google Sheets returned the following error message: 400 Unable to parse range: AAA4!R2C21:R100C20
And getting this same error regardless of how many columns and rows are in the file. Regardless if it's “Basic” import or “Advanced”.
Import Log files show this error and nothing else.
Anyone got Google Sheets import working? Or how do you import form Linear. Or should we stay with Linear?
Please sign in to leave a comment.
Hi Roman. Thanks for submitting your request to us. After looking at the logs, it seems like the problem starts when the import gets to the U column in the worksheet. It may be empty or something else could be the problem, so perhaps removing this column might help (if there is no useful data in this or other columns after U).
Overall, the Google Sheets import should work, and we are ready to investigate it if for some reason it doesn't work as expected for you.
Empty columns not supported? Or specific columns can not be empty? I found it very frustrating because there’s no information.
Error message points to invalid call made from importer, but you’re saying it’s user’s fault!
Why not at least add that bit of information to the error message and not making me waste 2 days of my time.
Yes, but this error is returned by Google Sheets, and the import in YouTrack displays it as is.
For now, we are not sure what caused this, so we would be happy to look into it further if you could share more information about the spreadsheet that you imported in the ticket that you submitted. We might file a request for improvement to this import once we understand the issue better, so your cooperation here would be much appreciated.
I am trying to import data from one instance to another via spreadsheets. Encountered the same error message. Removed all other rows and tried importing only the first row, resulting in the same error. No blank columns in the row. I am trying to import data from version 2019.2, Build 58831 to the newest available version.
This is the case when it was implemented and tested with specific sheet document, and not tested in a real world scenario with variety of software exports.
You lost me as a customer as a result of that, and how many others would even send feedback.
Hi Vishnu Soman,
To find out what's causing the error, we'll need some more information from your side, in particular the import logs and the Google Sheets file. May I ask you to submit a support ticket with this info here: https://jb.gg/ytsup? Our support team will investigate the issue further and suggest a fix. The import logs can be downloaded from the import configuration in YouTrack by clicking the “Download import log” button.
Roman Roan,
We're very sorry about your experience with the import feature. The structure of the imported data can vary greatly, so covering each scenario doesn't seem possible. We would appreciate a chance to fix the issue you encountered, but we'll need to investigate it further first. So, if it's convenient for you, please feel free to submit a ticket with our team here: https://jb.gg/ytsup.
Hi Julia Bernikova ,
I cannot share my data with your team. However, you could try this with an exported sheet from version 2019.2 - Build 58831, converted into Google Sheets. I tried with multiple sheets with varying number of rows, and got this error every time.
Hi Vishnu Soman,
2019.2 is quite a dated version, so the structure of the exported file needs revising before you can use it for import. I suggest you reformat the file as mentioned in the documentation. If you need any help with that, please remove the sensitive data and share it with our team - we'll let you know what needs changing.
I am still getting this error with the YouTrack Cloud version.
Why can’t we just upload a CSV file directly? That way the import would not depend on Google’s response.
Without a reliable import option (even the Jira API import isn’t working anymore), migrating to YouTrack is really difficult, to be honest.
This is basically a blocker for new users who want to switch to YouTrack.
Hi Calvin
If you face any particular issues, it will be great if you contact us directly via the link: https://jb.gg/ytsup
Please attach the import logs, the screenshot of the configuration and the particular error you face.
Hi Lena Vostrikova ,
To be honest, at this point I rather wait for the Jira import to be fixed. I tried the CSV option because the Jira import didn't work
Hi Calvin
Are you referring to the particular issue we already know about? If yes, please share a link, and I will point our developers' attention to it. If you haven't contacted us regarding the problem yet, we ask that you create a private support ticket and describe the problem in detail.
Hi Lena Vostrikova ,
That's correct. You are already working on the fix here: https://youtrack.jetbrains.com/issue/JT-91131
Hi Calvin
You are right. We are working on this issue with the highest priority. Please stay tuned for the updates.
Hi,
I'm having the same Issue with Roman, trying to import a google sheet via Youtrack and its giving me the error “[423-4] Google Sheets returned the following error message: 400 Unable to parse range: Sheet1!R2C21:R100C20”, The sheet has data in already from copy and pasting of an excel spreadsheet. I Don't understand the error because the sheet I'm uploading has nothing different in the columns 21 and 20 all the way from Row 2-100 than all the other rows and columns.
Hello Slashacute!
Stan from YouTrack Support here. I sent a reply to you in ticket #8184944 earlier.
To avoid this error, please add the field type for each field by adding the field type in parentheses next to the column name. Please see the field mapping guidelines here.
The error you received occurs when the import script tries to recognize field types that are not explicitly set in the sheet's columns. I've identified the bug and reported it to our developers.
Have a nice day!
Years later and nothing? People are still trying to use Youtrack and migrate data to your product and the main avenue of that is Google sheets. and you still haven't fixed this fundamental import issue.
Hello Roman Roan,
Thank you for following up!
The solution for 400 Unable to parse range error is planned for release with a wider import overhaul, however I cannot give an ETA at the moment. In the meanwhile, the import works without issues when the field type is added to the columns name.
Don't hesitate to reach out anytime if you have any questions or encounter any difficulties, we're always glad to help. Have a nice day!