Populating pick lists from an existing or custom table.

The ability to add a field which can be populated by a pulldown from a predefined list on an incident, CI or other form is a valuable one. Currently I am not able to find a way to do this without using a picklist in a template. Several use cases for this exist. In the case of department this means we need to maintain two department lists. One on the department table and another on a pick list. This is far from best practice as it duplicates work, increases the possibility of error and does not allow reporting on additional fields in the department table, The power of a relational database is lost.

I can appreciate the current efforts to import into a picklist from a CSV though the ability to link a field to another table which is editable from the interface allows for the greatest flexibility. Additional information can be stored against those records such a responsibility matrix, locations or contact information. This information can be displayed to the agent quickly without the need to dig into other systems.