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 AM ON JIRA SERVER
I want to set the value of Target Start to be the present day, but this JSON is returning an error saying the value has to be a string. Anyone can help?
So... this may just not be possible:
As @John Funk wrote back in Nov 2020:
And @Bill Sheboy found:
According to this Code Barrel ticket, the Portfolio and Advanced Roadmap fields are not supported yet:
Alas, that Improvement request still appears to be open. :-{
Same ticket in Atlassian's system: https://jira.atlassian.com/browse/JIRAAUTOSERVER-159
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello the attr for the field "Target date" is "customfield_11001" you can export to XML any Epic or Task and check this...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also, it is a locked custom field. This custom field is created and required by Portfolio for Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Looks like "Target Start" is just a date (without a timestamp)? Maybe try:
{{now.jiraDate}}
Some other functions you might try are here: https://confluence.atlassian.com/automation/date-and-time-functions-993924864.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just tried that and got the same error.
Here is the error I am receiving:
"(Operation value must be a string (customfield_14202))"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It would be helpful to do some debugging to see what an existing value looks like (to Automation).
So I would create a new rule with a Manual Trigger that doesn't do anything but do a Log action with a message of:
Target Start: {{issue.customfield_14202.value}}
And then manually trigger the rule from an issue that already has Target Start set, then look at the Audit log for this new rule to see what a "valid" value looks like.
I suppose you might also try:
{{now.toString}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tried that, and the Target Start is set on the ticket, but the audit log shows up empty. Photos attached.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess I would also try seeing if you get anything for these Smart Values:
{{issue.Target Start}}
{{issue.Target Start.value}}
{{issue."Target Start"}}
{{issue."Target Start".value}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh and also: {{issue.customfield_14202}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
{{issue.customfield_14202}} worked and returned this value
2021-11-02
How do I take this information and move forward with configuring the automation
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.