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.
I've been bedeviled by these errors, that have always happened after I created a field and didn't associate it with this or that entity, or didn't include it in a screen. I created 8 or so fields, and it would be nice to get a message that provided more information.
I realized the error was my experiment with using smart values instead of %%CURRENT_DATETIME%% in setting a date in a post action in the transition. I can't remember whether the transition can change the value dd/[month spelled out]/yyyy, but I figure I can do it in an automation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.