Extracting input from a custom field

Akinola Oke

I have a custom field which contain both text and number in this form "sehr unwarsch., 1", however I would want to extract the number at the end and populate it into another custom field.

What argument would be appropriate in this case? Should the custom field name be used instead of the customfield number.

Would this be appropriate {{issue.customfield_12200.substringAfter(",").trim()}} as I am not getting the expected result.

Or is it more appropriate to use the custom-field name itself.

 

Paul Glantschnig _Appfire_

Hi @Akinola Oke,

Referencing the field by its ID (customfield_12200) is IMO the most reliable approach, so syntax should be fine.

When nothing comes through, the cause is usually the field type:

• Is the source a single-select / dropdown field? Those don't return a plain string, they return an option object, so the text functions have nothing to work on. Reach the text through .value first: {{issue.customfield_12200.value.substringAfter(",").trim()}}
• Check the destination field. Writing into a number field stores 1 fine; if it's another select field, the option 1 has to already exist or the value is silently dropped.

The quickest way to diagnose: add a temporary Log action that prints both {{issue.customfield_12200}} and {{issue.customfield_12200.value}}, run the rule, and read the audit log. That shows you exactly which form holds your text, and you can plug that into the extract.

Best, Paul