I want to update a single line text field using automation.

[Gayathri B]

Hi team,

I am creating an automation, where in when the fix version is released - the issue ticket gets transitioned to "Done" status. Alongside this, I also update a date field with the release date. 
Once this happens, I will compare a due date against the release date to know if we have delivered it before the due date or after and update a text field with an automated comment. 
I want to understand how to update this text field through automation as the syntax is bit confusing for me. 

[Bill Sheboy]

Hi @Gayathri B 

For a question like this, please post images of your complete automation rule and the audit log details showing the execution.  Those will provide context for the community to offer suggestions.  Thanks!

Until we see those...

What part of the syntax is confusing to you?  For a text field, you can try the Edit Issue action, select your field, and set the value.  Some fields may not be listed, in which case you can use the advanced edit with JSON features.

Kind regards,
Bill

[Gayathri B]

[Gayathri B]

Thank you @Bill Sheboy . 

you can check through my conditions. Once all conditions go through, i want to update the text field called Commitment as "Achieved" or "Delayed". 

This is my requirement. Kindly help how to correct it

[Bill Sheboy]

Would you please post an image of the audit log details, showing the rule execution?

And are you certain that the Commitment field type is text?

[Gayathri B]

Hi @Bill Sheboy Attaching the screenshots here. 

There was one problem that I just identified through the answer explained here 

The automation itself was not getting triggered for the test tickets that I had been creating. Once the problem was solved through the solution given in the above link , I tested the automation further. 

I can see that automation is triggering now, however it states that the condition mentioned does not satisfy. In my opinion it does satisfy. I am not sure what am i missing here. Pls help. Thanks!

[Bill Sheboy]

Thanks for that information!

Here is what I hypothesize is happening: the way you are performing that date comparison is preventing the expected results due to date/time formatting.  (Sadly, not all things represented as "dates" or "date/times" are of the same format in Jira.)

We can confirm that by changing to use an advanced compare condition and forcing the dates to comparable formats/values.  Please adjust this to match the correct smart values for your fields...When in doubt, try this linked how-to article to identify the smart values for fields.

• advanced compare condition:
  • first value: {{issue.Prod Release Date.jiraDate}}
  • condition: less than
  • second value: {{issue.duedate.jiraDate}}