MisterB
Champion Level 3Joined 5 years ago
User Profile
Champion Level 3
User Widgets
Contributions
Re: Maximun test cases downloaded to Excel
I've downloaded into the thousands, so I'm sure it's not the number of records that's causing this issue. I assume when you say download, you are using the Test Case > More > Export feature. That should work fine. As should downloading a generated report. If you continue to have this issue I would contact SmartBear SupportRe: Zephyr Scale make lost main menu when reached
Hi, my guess would be a browser issue as I assume it's not affecting all users. Perhaps you have a browser extension running that is causing the issue? Things you could try: Check if other users in your company have the same issue - it might help you pinpoint the cause if you find someone not experiencing the issue Clear your browser cache and re-try Zephyr Try opening Zephyr in Private/Cognito mode with no extensions Try using another browser Contact SmartBear SupportRe: UTF-8 file import issue for custom fields
Hi! Thanks for sharing this issue - it's good to know that it exists. I have tried to make it work using UTF-8 encoded Excel, Notepad, and Notepad++ CSV files and have shared the results below. It seems that Zephyr is doing something to the encoding of text in Single Line custom fields as it's not an issue in Multi Line fields. So, you can work around this issue by using a Multi Line field, but I would also raise it as a bug with SmartBear Support to fix. Source data: Ö ä å test ✘ Single line: Ö ä å test ✔ Multi line: Ö ä å test Source data: "Ö ä å test" - same data surrounded in double-quotes ✘ Single line: "Ö ä å test" ✔ Multi line: Ö ä å testRe: Uploading CSV file throws an error
Hi, I can try to help. If you haven't seen the relevant Zephyr Help page you can read that here To verify that a 'good' file does import I would try importing a 1 record CSV file for the least amount of fields needed, so all you need is 1 column of data which you would map to the Name column. That really should work and prove that everything works as it should. From there, I would add 1 row of your import file with all the fields you are importing, and see if that works. If it does, expand until you hit the error. When you hit the error check your data content - or you could do this first - and look for carriage returns, other delimiters just general weirdness. It'll be something like that. Opening the CSV file in Notepad or another basic text editor with word wrap disabled might be easier. When viewed like this you can scroll left<>right and it becomes pretty obvious when a row of data looks different to the others. Here's some info I found on problematic characters when parsing CSV data: Problematic Character / Issue Why It Causes Issues How to Fix It Comma (,) Treated as a column separator; unescaped commas split fields incorrectly. Enclose affected fields in double quotes ("like, this"). Double Quote (") Used to wrap text fields; unescaped quotes confuse parsers. Escape with another quote ("He said ""hi"""). Newlines (\n, \r\n) Treated as a new row even inside a field. Wrap the field in double quotes ("Line 1\nLine 2"). Delimiter Collisions Custom delimiters (e.g., ;, ` , \t`) can appear in text and break parsing. Unescaped / Inconsistent Quotes Mismatched or malformed quotes throw off the parser. Ensure consistent quoting and escape double quotes properly. Null Bytes / Control Characters Parsers may reject or crash when encountering binary or control characters. Sanitize the data—remove or encode problematic characters before writing the CSV. Encoding Issues Wrong encoding (e.g., not UTF-8) can corrupt non-ASCII characters. Use UTF-8 encoding (optionally with BOM) when exporting the file. Extra / Missing Columns Parsing breaks if line structure is inconsistent, often due to the issues above. Identify and fix malformed rows with unexpected column counts.
