You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
I am trying to add a condition to a workflow. The condition is to validate if the issue's parent link issue has certain custom fields populated.
Here is what I could figure out so far:
issue.customfield_10018.value!=null
where customfield_10018 is parent link field.
Even above code does not give the expected output. The parent link on issue is populated but the above Jira expression keep returning 'false'.
In case you're still looking, this Advanced Compare Condition should work, with this smart value - {{issue.Parent Link.<Field>}}
I just tested this with Assignee, and it worked fine.
If you'd like more specific help with formatting the Condition, let us know!
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am also trying to access the Parent Link field (the field provided by advanced roadmap) in Cloud.
I am trying to create a Scriptrunner Validator that uses Jira Expression language instead. And the issue.customfield_XXXXX.value !=null is not working (but for other usual custom fields, this is working)
Even issue.customfield_XXXXX.key !=null is not working.
I think the smart value advanced comparison is only applicable for Automation right @Stephen Wright _Elabor8_ ??
Are you aware if Parent Link field is accessible via Jira Expression?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No worries @Susheela_Kushwaha - let us know how it goes!
---
@angelicagavino - I think there's limits in Expressions like in JQL. Because "is not EMPTY" or "Null" is not an available option for Parent Link in JQL, so might be similarly unavailable in your use case.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Adding here for everyone's benefit (and to whoever will come across with same issue).
Turns out that you should use .data
Example:
issue.customfield_12345.data !=null
where 12345 -> ID for Parent Link custom field
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.