Automation Error - No fields or field values to edit for work items

[Ashleigh Hamilton]

I have set up a simple automation for a JPD project to date stamp a field when an idea is transitioned, but am receiving the error "No fields or field values to edit for work items" for the date field. I have tried it with smart values in the automation field {{now}} and {{now.jiraDate}}. I have also tried using JSON: 

{
    "fields": {
        "customfield_0000":"{\"start\":\"{{now.jiraDate}}\",\"end\":\"{{now.jiradate}}\"}"
}
}

But I keep getting the same error. I noticed that I also received this error for another automation where I set the 'Resolution' field to 'Done.'

Is this a bug, or am I doing something wrong? I know that there is currently a rule delay incident, but my automations are running; they just aren't populating the fields, so I am not sure if this is related. 

 

[Bill Sheboy · Accepted solution]

Hi @Ashleigh Hamilton 

First thing, Atlassian is recovering from an automation outage and perhaps that is impacting rule behavior, in addition to delayed rule execution.  Please look here to follow progress on it:

https://jira-software.status.atlassian.com/incidents/8l2pc9p1fr04

Next, you are showing / describing symptoms from multiple different rule issues.  I will try to identify them so you can work through them...

The JSON expression you show to set a JPD date field is correct.  One reason that could fail is if the rule actor does not have permissions to edit Ideas.  Has anyone changed the rule actor in the details at the top of the rule?

For the Resolution field edit attempt, that may happen if the Resolution field is not available on the create / edit issue view.  Have you checked that?

Finally, there is a built-in field named "Start date" at the global level, and as your rule is shown I would expect it to work.

• Do you have multiple fields named "Start date", and so the rule is confusing which one to use?
• That is, did you name your JPD date field "Start date"?

Kind regards,
Bill

[Ashleigh Hamilton]

@Bill Sheboy thank you for the insight. You are right. It looks like the 'Start date' used in the automation is the Global Field, and unfortunately, that field is not available to JPD. I changed the name of my custom field, but when it didn't show up, I realized that JPD automation still does not support date fields. 

I am using the resolution field for JPD as well, and you cannot configure it. I was following was others said in this post: https://community.atlassian.com/forums/Jira-questions/Does-Product-Discovery-support-resolution-field/qaq-p/2369608/. 

[Ashleigh Hamilton]

Once I switched the custom field ID to that of my new date field, the JSON worked! Thanks for your guidance. 

[Bill Sheboy]

Awesome; I am glad to learn it is working!  Please consider marking this question as "answered" to help others with a similar need find solutions faster.  Thanks!