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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,777
Community Members
 
Community Events
176
Community Groups

Help with smart values for lookup issues

Edited

Hi

I would need help in determining what is wrong with my smart value/ JQL for lookup issues automation. 

The logic of the automation: 

  1. If a client creates "Upgrade task"
  2. Lookup for issuetype="os update" AND customfield_123 (random customfield name)
  3. Then comment on issue with issue key and customfield_456 (random customfield name)

customfield_123 contains company name so ideally, the JQL should find only those "OS updates" which match the value of customfield_123 that is present in the trigger issue. (Deploy advanced compare perhaps?) 

Problem:

  1. When the smart value for customfield_123 is inserted into JQL, the comment contains the issue key for the trigger issue (i.e. Upgrade task), not for OS update/-s
  2. When the smart value is deleted from JQL, the search returns a list of "OS upgrades" (correct) but naturally, the output is not limited by the value of customfield_123

Automation:

2022-08-02 12_48_24-Window.png2022-08-02 12_48_29-Window.png

 

1 answer

1 accepted

0 votes
Answer accepted

I was able to achieve what I wanted. The JQL was not correct in terms of syntax. Here is what worked:

issuetype="os update" AND "company name" ~ {{customfield_11943}}

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS

Atlassian Community Events