Jira automation does not work for some accentuated fields

[Vincent DESOUTTER]

Hello,

when trying to create an automation rule with some custom fields, the rule does not apply correctly.

Ticket # 1 :



Ticket # 2



We have a rule to update the 'Story Points réel' 



But the ticket resulting value is always 0:



I have tried many different fomulas, even with the customfields_XXX, but still not working.

It detects the right tickets in the lookupIssues, but the formula is not well computed.

I have tried with the 'Story Points' field in the formula and it works fine (the fields 'Story Points réel' is well updated).

The difference between the 2 fields is that the 'Story Points réel' is not restricted to specific projects/ type of tickets whereas the 'Story Points' is restricted to the given projects and type of tickets.

Do you know why the formula does not work ?

Can it be related to the 'é' char in the variable ?
Can it be related to the field definition?

Thanks for your help.

Vincent

[Dick]

Hi @Vincent DESOUTTER Welcom to the Atlassian Community.

Sadly, the custom fields in the Data Center lookupIssues function haven't received the love they deserved yet. It will not work. 

You can read a workaround in the answer to a community question that @Bill Sheboy kindly provided earlier.

Kind regards,
Dick

[Bill Sheboy]

Hi @Vincent DESOUTTER -- Welcome to the Atlassian Community!

Adding to the suggestions from @Dick here are more details I wrote on using the REST API for a situation like yours:

https://community.atlassian.com/forums/Jira-articles/How-Can-I-Sum-Up-Multiple-Issues-into-a-Parent-Number-Field/ba-p/2882712#M16701

Kind regards,
Bill

[Manon Soubies-Camy]

Hi @Vincent DESOUTTER and welcome to Community!

If using the customfield_XXX smart value doesn’t work either, it’s unlikely the issue is due to special characters like the "é". Can you please confirm the type of custom field for "Story points réel"? Is it a number custom field, a text one?

Based on your tests, it looks like "Story points réel" might be a text field. In that case, you'll need to convert the value to a number:

{{lookupIssues.Story points réel.asNumber.sum}}

I highly recommend using Log actions to debug the rule and understand what values are being returned:

Hope this helps!

- Manon

Edit: I just noticed you're on Jira Data Center, so my answer might not fully apply. I unfortunately don't have access to a Data Center instance to test it out.

[Vincent DESOUTTER]

Hello,

thanks for your answer,

I have manage to add some logs and I confirm that the values from the 'Story Points réel' field are not accessed.

Coming from that logs :

I also confirm that both fields are numerical format :



(Champ numérique <=> Numerical field)

I am totally lost.

Thanks for your help.

[Jaime Escribano]

Good morning Vincent! Welcome to the community!

There is an easy way to find out if the accentuation is affecting your automation.

Could you try out changing the smartvalue from {{lookupIssues.Story Points Renée}} to {{lookupIssues.customfield_XXXX}} where XXXX is the ID of your custom field.

That way we can discard any weird accentuation shenanigans.

To find out your custom field ID you can follow this documentation: Learn multiple methods to obtain custom field IDs for Jira and Jira Service Management products. | Jira | Atlassian Documentation

Hope that was helpful!

Best regards,

Jaime Escribano

[Alex G]

Hello Community,

I'm working with Vincent and I can confirm the ID is "10166".

We therefore tested two queries: "{lookupIssues.Story Points réel}}" and "{{lookupIssues.customfield_10166}}", but neither worked.

Regards
Alex