The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

AQL with currentProject() doesn't work in cloud

Christof Hurst
Contributor
July 26, 2023

Hi, 

we have an Assets objectType with an attribute of type Project called "Projekt".

When trying to limit the results in a customField we want to use Filter issue scope (AQL): Projekt = currentProject() as it works in Jira DC. But in cloud the results are empty.

What can we do to limit the assets depending on the actual project?

BR Christof

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Answer accepted
Christof Hurst
Contributor
July 27, 2023

According to support:

[...]

In Cloud while that function does not work we can access pid - the Project Id or Name through a placeholder.
https://support.atlassian.com/jira-service-management-cloud/docs/configure-the-assets-object-field

${pid.id} for the id of the project
${pid.label} for the Name of the project

-----

That works but only with pid.label and LIKE operator.

Filter issue scope (AQL): "Projekt" LIKE ${pid.label}

Christof Hurst
Contributor
August 9, 2023

Update: Atlassian changed a bit and now the ${project} value has to be used:

Filter issue scope (AQL): "Projekt" IN ${project}

or

Filter issue scope (AQL): "Projekt" = ${project}

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events