automation_id appears to be limited to 250 characters

andrewgbell commented 2 years ago

TestRail CLI Version

1.3.0

CLI Environment

Windows 11 Pro, Mac m1

TestRail Version

7.5.4

TestRail Instance Type

Professional Cloud

Current behavior

Trying to import with long test cases gives the error

Field :custom_automation_id is too long (250 characters at most)

Desired behavior

the import should succeed regardless of automation_id length, as no limitation is mentioned in the documentation.

More Details

I can't find anything in the documentation that mentions this limitation when creating the automation_id field as a string. Is there any workaround to this, we have many test names which go over this limit so it would not be an easy task to reduce below.

When we try this with shorter test cases, the import works without problem.

A possible solution would be to change automation_id field to Text in place of String potentially, though it's not something we've tried, or whether this would be a workaround.

shashankgumte commented 2 years ago

I have created automation_id as custom field in testrail and selected data type as text as workaround.

andrewgbell commented 2 years ago

Didn't work for us, get the error: Field :title is too long (250 characters at most).

When automation_id is a text field.

shashankgumte commented 2 years ago

@andrewgbell This is working for us previously I was using string data type then converted to text data type . Now it is accepting more than 250 characters in automation_id custom field.

ncbullock commented 2 years ago

@shashankgumte how were you able to "convert" from a string type to text type? Once a custom field is defined, the system will not allow the type to be changed. We also tried deleting the custom field so we could re-create with the text type, but can't find any way to delete a custom field.

dominicwilliamslandmark commented 1 year ago

Had the same issue and got in touch with the TestRail support. They stated that this is by design and I'm welcome to use the API instead which has a limit of 4000 characters. They provided me the reasons why it was implemented with this limit and have also said they've raised a feature request.

Design decision: The CLI tool has been designed to have a smaller limit on certain fields to encourage users to provide concise and specific information. This can help to reduce clutter and make the tool more user-friendly.
Performance: The CLI tool limit the length of certain fields to ensure optimal performance. Larger fields usually take longer to process, which could impact the overall performance of the tool.
Compatibility: The CLI tool is designed to work with multiple versions of TestRail, and may have a limit on certain fields to ensure compatibility with older versions of TestRail.

d-rede commented 1 year ago

Hello everyone,

Unfortunately, we didn't anticipate that using a string type field could cause such inconvenience due to size limitations. We will change our documentation and start suggesting that users opt for a text type field.

@ncbullock while it may not be ideal due to the loss of all field data associated to the field, TestRail does allow deleting and re-creating custom fields with the same ID. You can delete the field under Administration > Customizations > Case Fields by clicking the red X icon.

@andrewgbell string type fields also look like text, are you sure the field is configured as a text type?

andrewgbell commented 1 year ago

Hello everyone,

Unfortunately, we didn't anticipate that using a string type field could cause such inconvenience due to size limitations. We will change our documentation and start suggesting that users opt for a text type field.

@ncbullock while it may not be ideal due to the loss of all field data associated to the field, TestRail does allow deleting and re-creating custom fields with the same ID. You can delete the field under Administration > Customizations > Case Fields by clicking the red X icon.

@andrewgbell string type fields also look like text, are you sure the field is configured as a text type?

Yes. Though due to limitations in the trcli we've ended up using our own integration in the meantime.

bitcoder commented 11 months ago

We'll add a note on the TRCLI documentation to make the current behaviour clear and provide the text type field suggestion

AlexTRGit commented 7 months ago

I have the same issue as described above [Field :title is too long (250 characters at most)]. We are trying to Upload automated test results from JUnit reports. From TestRail, we deleted the automation_id - type: string and re-created it with type: Text but we got the same error message. Is there someone who resolved this issue and can advise how we can fix it?