Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Request Type in Filter Issue Scope of an Assets Object Field does not work

In a Assets Object Custom Field I want to create a Filter Issue Scope AQL referencing the Request Type of the current Issue. Request Type Field is of Type "Customer Request Type Custom Field".

I've tried a lot but with no success: 

  • "RequestTypes" LIKE ${}
  • "RequestTypes" LIKE ${customfield_10700}
  • "RequestTypes" LIKE ${}
  • "RequestTypes" LIKE ${customfield_10700.requestType}
  • "RequestTypes" LIKE ${}

Following AQLs do work:

  • referencing the Issue Type: 
    Filter Issue Scope (AQL): "RequestTypes" LIKE ${}
  • referencing another text only custom field:
    Filter Issue Scope (AQL): "RequestTypes" LIKE ${customfield_13700}


Is it not possible referencing a complex custom field from an AQL ? Or does anybody has a solution for this?

We are running Jira 9.4 / Service Management 5.4. 

3 answers

@Andreas von Euw Question...

How did you get the Customer Request Types to import into Assets? The Jira Importer doesn't bring them in.....

I didn't. My "RequestType" Attribute in this sample was just a dump text field with a list of request type names. 

I have used a scripting app (powerscripts) to write functions which use api calls to build the request types as asset objects. 

Yeah, I thought about writing a Job in ScriptRunner. You would think the Assets Jira App would pull them in automatically.....

Also, try ${customfield_10700.label}. That seems to work for asset object types.

I have the same problem.

Have you found the solution?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events