I have an automation rule that set a custom field (called `Implementation_started`) to the current timestamp when the issue comes in a specific state.
For that, I used the "more option" part of "update a ticket" action:
That automation rule worked well until the 2nd of February as you can seen in the audit logs:
And then I began to have some errors.
The message is: "Supplementary fields contains one or more non valid fields for the section "update" or "fields": Implementation_started"
I went to verify that this field is still available on the ticket (for instance here the MHC-1852) and it is the case:
(in the print screen, the value is set but I filled it manually...)
Do you have an idea of the issue?
Thanks for your help!
I'm not sure if this is related to the error, but for these more advanced field actions I usually use the field ID rather than the field name, so there is no ambiguity in which field is being set.
To locate the custom field ID for "Implementation Started" you'll need to be a Jira Admin and then:
This would then make your logic:
^ I would give this a try first, and see if it fixes the issue :)
Thanks for your answer but we finally made it work again.
There should have been an update on Jira automation tool, because now I am able to find the custom fields in the dropdown list:
So I don't need to use the "more option" part of this feature.
And doing like this make it work again :-)
Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events