Per-organization/per-customer field value selection

[Josef Kejzlar]

Hello

we need some way to limit organization/customer what values can select when creating an issue. In another way, we need customer to select what application the issue is connected with, but one customer can not see applications of another customers.

To explain our whole situation:

We have hundreds of service customers, grouped in organizations. To every organization we develop several applications (from 1 to 5). Every application is unique and one customer/organization can not see applications of another organization.

Every service issue has to be connected to one application (or more applications if possible) of the given customer/organization.

I think I'm unable to use custom select field, because other customers/organizations can see all choices.

I was thinking about using Components, but components are not linked to Organizations/Customers either and customer can choose from any component.

How to model this situation? I believe it is not uncommon to have per-customer or per-organization choice field where one can not see all options.

[Lucas Knorr]

@Josef Kejzlar

one solution could be to change the displayed field options depending on a group/organization membership. This would be possible with the Scriptrunner (https://docs.adaptavist.com/sr4jc/latest/features/behaviours/behaviours-supported-fields-and-products) plugin.

Otherwise, it would also be possible to define a separate request type for each organization with a separate selection field for the application (it is possible to restrict request types to groups/organizations).