What is the best way to handle a "sub-customer" type of a list?

[Jared G]

Our customers are other businesses, and the work we do is all around their employees (think payroll consulting).  Therefore, we use a customer portal to interact with the business owners, general managers, etc... but we would not use each individual employee as customer contacts.

We are seeking a solution to list employee names on the Jira ticket which we do have a custom field for this, both first and last name.  However, we're concerned about data integrity as they are free form fields, so someone could type in "John" while another types in "Jon".  We therefore would love to use a drop-down style list, but this would involve a Jira admin maintaining lists of employees in a custom field.

Looking for solutions where there could be a list of employees to choose from, but housed in a location that could be edited by users.  We would need the field to be reportable say from a Jira filter.  Any suggestions on this, or does anyone know of any 3rd party apps that might support it?

[Esteban Diaz]

Hi Jared G, 

You can try using an Asset Schema to import and keep an updated list of employees, adding a column for the Organization (Company) to filter employees by the company.

Then, create a custom asset field that shows the filtered users based on the organization to which your customer belongs to.

Cheers, 

Esteban

My LinkedIn 

The Atlassian Guy channel