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!


Using AQL i would like to lookup a word in a string


   We have a complex scenario where we read keywords to the ticket summary and determine the component and auto assign the ticket. Current this is all a manual multi-step process of IF-Else statements. this is getting too big and hard to manage. Hence the idea is to use assets or a lookup table to determine the component based on keywords. 

  I was able toc create assets etc. but problem is in finding the keyword within the summary using AQL . Please let me know if anyone has a similar issue and have a solution for it. 



1 answer

0 votes
Marc Koppelaar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Sep 20, 2023

Hi @Ashok Shirppi 

This could be possible but, this would require a summary attribute on the objectType component in assets

For example, if you wanted to only show a list of components owned by the current summary, you could configure the Filter Issue Scope (AQL) field by typing objectType = “Component” AND "Owner" LIKE ${summary.label}.

Jira system filed are case-sensitive and must be typed exactly as below.

In your case I don't think this will work, as you don't use the full summary and the case sensitivity issue

I think you would need to create a more elaborate assets scheme and create custom fields, populated with assets data and let customers select there needs and assign issues based on this.

I hope this gives you direction, but I don't know if this is where you would like to go.

Thanks for your response. this will not work in my case as most of the tickets we receive is through the email channel and we would like to parse out the key words from the summary to determine the Components. 

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events