Hello,
We currently experiment with an object sheme (JSON import) using two object types A and B. As far as I understand it is possible to restrict user access and visibility based on the object type. We would like to further restrict the visibility within the object types based on attributes. The background here is that we would like to refrain from using multiple object types.
E.g. Object type A has the attribute "test" with multiple possible values such as "foo" and "bar". So users being part of group X can only see the objects with "foo" and users of group Y can only see all objects with "bar".
Is there any possibility to realize this without having to split the object types into multiple ones via IQL and set the permissions there? Depending on the amount of values for the attribute "test" we would have to create many different object types or multiple custom fields with respective IQL restrictions. So to summarize we would like some form of dynamic permissions within an object type based on groups/projects.
Kind Regards,
Florian
Hi @Florian Nawrath ,
welcome to the Atlassian Community!
Unfortunately I believe the only possiblity is to split the object types as you've described.
It is possible to use a “hidden” property on the attributes, which allows you to hide attribute from the Insight users role, but this won't probably help you.
Hi @Hana Kučerová ,
That is unfortunate, still thank you for the fast answer :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have a very similar requirement.
I would like to select a group, which the limits the visibility of an object to that group only.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
With this, it is possible to restrict visability to only certain groups (that are mentioned in the object in an attribute).
https://support.atlassian.com/jira-service-management-cloud/docs/use-assets-query-language-aql/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.