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
{
"fields": {
"Estimated Drafting Hours": "{{issue.Group of Job}} == 'A' ? 8.0 : {{issue.Group of Job}} == 'B' ? 5.0 : {{issue.Group of Job}} == 'C' ? 3.0 : {{issue.Group of Job}} == 'D' ? 1.5 : {{issue.Group of Job}} == 'E' ? 1.0 : 0",
"Estimated Checking Hours": "{{issue.Group of Job}} == 'A' ? 1.5 : {{issue.Group of Job}} == 'B' ? 1.0 : {{issue.Group of Job}} == 'C' ? 0.5 : {{issue.Group of Job}} == 'D' ? 0.25 : {{issue.Group of Job}} == 'E' ? 0.25 : 0",
"Actual Drafting Hours": 0,
"Actual Checking Hours": 0
}
}
Hi @NAREIN CM
What is the context for using that JSON? Is this in an automation for Jira rule?
If that is the case, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!
Until we see those...
If that expression is being used in an automation rule, I suspect it is a syntax the rule action cannot parse. For example, you appear to be using conditional handling for setting the Estimated Drafting Hours and Estimated Checking Hours fields. Instead, please consider using conditional rule handling for the smart values: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.