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,456,341
Community Members
 
Community Events
176
Community Groups

Automation for custom field is not working: "without custom field set" condition ??

Edited
Hi All,
when I add a card to the List1 the checklist is not created although I am not notified with error. could the reason be that these conditions together will not work???
- Custom field type= Date
- Buttler code :"when a card in list "List1" without custom field "custfield1" set is added to the board, add an empty checklist named "test" to the card".

1 answer

1 accepted

0 votes
Answer accepted
Ryan Atlassian Team Mar 03, 2022

Hi Amro,

I tested out a similar rule, and this seemed to work for me. Could you check that the list name and custom field name are correct in the rule? These need to match exactly (in terms of capitalisation and spacing as well) for the rule to recognise these and execute the rule.

Alternatively you could use the trigger based on the card being added to that specific list, such as: https://share.getcloudapp.com/xQuqKDRR

Let me know how it goes!

Ryan

Thanks Ryan

Actually I was using another trigger expression than the one you shared in the screenshot, when I used the one you shared it worked for me. thanks

here I was using trigger 1 and when I used trigger 2 it worked. Screen Shot 2022-03-03 at 3.16.50 PM.png

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events