nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Different filter on Assets custom field for 'inside jira' and 'portal view'

Kevin Gérard

HI!

We've built a CMS system on Jira Assets, we've got some custom fields connected to it which will rely on automation to sync the appropriate data back to the other tickets fields.

Now i'm faced with a certain limit here.

When a customer uses the field on the portal, i need it to show only the data relevant to her/him. This works fine, as i've been setting it up in the custom fields context.

BUT if a service desk agent or colleague uses the field, she/he should be able to see ALL options.

The only option i see right now is adding a second custom field, but this would make everything so much more complex.

Accepted answers

Kris Dewachter

Hi @Kevin Gérard ,

I've encountered this issue previously in the past. I handled this by adding an extra attribute to the asset, indicating the usergroup which is allowed to see the asset in the custom field.

Best regards,

Kris

All comments

Marc -Devoteam-

Hi @Kevin Gérard

You have limited the options based on the context in the assets field context on the field.

So this applies to everywhere the field is used.

So also for the agent, so the agent needs to provide the related field as first, before using this field.

Otherwise an exact the same field is your only option, but in my mind this causes confusion on reporting.

Other option to try is to add an extra attribute referencing a groups of users (jsm-agents) and add this in the context of the field based on an OR clause.

Kris Dewachter

Hi @Kevin Gérard ,

I've encountered this issue previously in the past. I handled this by adding an extra attribute to the asset, indicating the usergroup which is allowed to see the asset in the custom field.

Best regards,

Kris

Kevin Gérard

Hi Kris!

Thanks for the suggestion, it's all a bit of a 'dirty' workaround, but eventually it works even better than expected!

This actually solves a BIG problem!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management