The current bulk update process in Freshservice, particularly concerning required fields, is a significant source of frustration and inefficiency. Users should not be forced to engage with data they don't intend to modify, especially when it leads to a time-consuming and error-prone experience.
Consider this common scenario: I needed to update a set of assets. The process required me to have two tabs open simultaneously – one to identify the mandatory fields and another for the export settings. I had to constantly switch between them, meticulously checking off all the required fields for export, even if they already contained the correct data.
After a painstaking export and extensive data manipulation, I attempted to upload the updated assets, only for the upload to fail because I had missed a required field. This meant repeating the entire export process, this time including the newly identified field.
The frustration didn't end there. Upon the second upload attempt, the process failed again due to an incorrect date format in a field I never even intended to modify. This forced me to reformat an entire column of data, further extending a task that should have been straightforward.
This convoluted process significantly hinders productivity. We should be able to perform bulk updates without being coerced into exporting, reformatting, or re-uploading data for fields that are either already accurate or irrelevant to our intended changes.
