Hello,
I have an object type called "Business Services" in which I added an attribute called "Related projects" which can hold projects.
I want to add an AQL to the filter issues scope so that only objects where a project is selected are available for the given project.
For example, in Object 1 I have added project ABC, I want this object to be available only when a ticket is being created in project ABC.
I tested one solution but this only worked for Agents. Portal only customer did not see anything for some reason.
This is the full AQL I used:
(object having inR("Jira User" = ${reporter}) or object having inR("User Group" having user(${reporter}))) and "Related Projects" = ${project}
I bolded the part that I added to the AQL which worked but only for Agents as I mentioned above.
Is there a way to implement this so that it includes portal only customers as well?
Adding a screenshot of the field configuration:
Hello @Adolfo Casari , can you share the the configuration of Roles for the schema for which this worked in your case?
It works for portal only customers as well?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In your own example, Business Service should have an attribute Related Projects of type Project.
With that I control on what JSM projects that service can be displayed or not. I also filter the objects by issuetype (i.e. request type) and jira group with:
"Tipo" = ${issuetype.label} AND "Grupo Afecto" having user("currentUser()")
Where Tipo is a select type attribute and Grupo Afecto is a group type attribute.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think you need to go to Roles in your schema where "Business Services" is and check that "Object Schema Users permissions for Jira Service Management Customers" is Enabled.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Adolfo,
If it is an issue with roles in the object schema, how come that customers can see and search for objects with this AQL:
(object having inR("Jira User" = ${reporter}) or object having inR("User Group" having user(${reporter})))
This AQL is only missing the part referencing the projects.
Could it be related to project permissions maybe?
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.