Automation error - Error while rendering additional fields.

[Theis Joergensen]

Hi All, 

I am trying my luck in here after hitting the triangle of death with AI. 

I am trying to setup an automation, which i believed would be simple.... 

Ticket A - linked to B

Issue type: SLA incident

Trigger: transition to QA verified

Field value to be copied: Labels (if it contains SDK) - (label-type field)

Ticket B - Linked to A

Issue type: Incident -1

Field where value should be copied to: Fix Version - (plain text field)

As mentioned above I am trying to copy a label if containing "SDK" from ticket A to B when ticket A is transitioned to "QA verified"

I am running into this error:

AI have tried solving it with JQL conditions and other types of conditions between trigger and branching but it all result some kind of issue. 

I worked once but the value in ticket B was shows like this: { "fixVersions": [] } while in ticket A it showed as SDK 2.5

Any help is appreciated!

[Bill Sheboy]

Hi @Theis Joergensen 

Please let me hypothesize: some AI-guesser tool suggested using that smart value expression containing filter(), right?

There is no filter function with smart value expressions in Atlassian Automation.  I strongly recommend not using any AI-guesser tools, even the one provided by Atlassian, for automation solutions.  Again I hypothesize: they do not have access to your specific configurations for the site, spaces, work item types, etc. and thus the guesses generated are often quite wrong, at best, and at worst cause irreversible changes to Jira data.  One would need to create a ridiculously long prompt to provide all the context, and even then I suspect it would be wrong.

Back to your question...

Have you tried using the match() text function with a regular expression on the trigger work item Labels?  I recommend doing that before any branching, and storing the result in a Created Variable before using that variable in your Edit Work Item action.  Using the variable will prevent any racetrack timing problems with using complicated expressions in the advanced edit.

Kind regards,
Bill

[Theis Joergensen]

Hi  Thanks for replying. 

I have tried what you mentioned - and to test made an audit log just before the last step which fails. 

 

I can see that it does find the value and it state the last step is succesfull

 

However, the field remain empty. 

I actually start believing the issue, or perhaps its a limitation, is that the field type in the trigger issue is standard label field, while on the linked issue it's a plain text field. 

Do you know if there is a solution to this or if i simple need the hard route of ensuring field types are the same?

[Theis Joergensen]

I also tested hardcoing a value in the last step:

{
"fields": {
"customfield_12818": "TEST"
}
}

And it worked just fine. 

[Bill Sheboy]

Thanks for those images as they show some potential problems.

The second condition appears to be a JQL condition, but what you show is not valid JQL.  As an alternative, please try:

• remove the JQL condition
• create the variable to extract the desired labels containing "SDK" 
• after that, add an Smart Values Condition to check if the variable contains anything before proceeding
• inside the branch, use the variable to set the custom field value

[Theis Joergensen]

 @Bill Sheboy 

After a bit more trial and error i managed to get it to work with following setup. 

 

Thanks for your help