Bulk Imports on 6.X should disregard case when case sensitivity does not matter

Story Idea:

As an Implementation Engineer, I would like all fields where case sensitivity is not relevant on a CSV bulk import to disregard the case.

Description/Example:

In a Groups import, the Call Forwarding When field requires either 'all' or 'unanswered' in order for the radio button to show up as configured for one or the other in the WebUI. If 'All' or 'Unanswered' is used in the CSV, then this won't show up properly in the WebUI. As there is no meaningful difference between upper or lower case on this, it makes more sense for that field to be case insensitive (either WEB ticket or PFM depending on how this could be implemented).

  • Guest
  • May 1 2020
  • Attach files