Is it possible to display a specific field in the portal based on the client?

Question

We work with partners and each partner has its own list of customers. I am creating one portal per partner because I do not want the other partners to see the list of customers from other partners.

I would like to have just one portal for partners and depending on the user that is creating the ticket, to display the field of customers based on their organization.

Is that possible?

Joseph Chung Yin · Answer

@Adriana Fitch -

Excellent suggestion by @Mark Segall

Another way you may consider is setting up different projects and lockdown visibility of the projects to different organizations of customers.  This can be achieved by project settings >> customer permissions.

The benefit of doing this is each project and its issues are only visible by the specific set of customers.  Remember that there is only one instance of the portal UI for all of your customers, but under the same portal env one can host one or more projects (I am sure that you already knows about it)

If you just want to have one project for all of your customers to use, but wanting the different fields or field's dropdown list option to be based on specific value, then you may want to take a look at

* ScriptRunner for Jira (https://marketplace.atlassian.com/apps/6820/scriptrunner-for-jira?hosting=cloud&tab=overview) add-on. 
* It has a separate component named Behavior (https://marketplace.atlassian.com/apps/1228522/behaviours-scriptrunner-for-jira-cloud?hosting=cloud&tab=overview) add-on which is free, but you must have 1st add-on (paid) installed to use it.

Those add-ons can support your needs based on my knowledge and experience.

Hope this also helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

Mark Segall_iqztfr · Answer

Hi @Adriana Fitch - The best way to handle this is by upgrading to JSM Premium and taking advantage of Assets.  You would have an object architecture like this:

* OBJECT 1: List of partners 
* OBJECT 2: List of partner users (An attribute would be added to reference the respective partner)
* OBJECT 3: List of Customers (An attribute would be added to reference the respective partner)

From here, you'd be able to use an Asset field which can be configured so that it only shows the list of customers based upon the current logged on user's partner affiliation.

Note - There will be some upkeep with this or some custom work to ensure that every time a new customer/organization is added, it creates corresponding Partner/Partner User objects.