structure: cannot access custom field (with space and special character) from parent

[Ludovic Boudinet]

I have a structure to list sub-task. In this structure, I need to display a couple fields from the parent which is a "Story".

I defined a variable "this" as parent and then I can access this.summary and this.status.

But I canno't access this."ABC no." which is a custom field with space and special character. Is there a solution for this ?

[Stepan Kholodov _Tempo_]

Hello @Ludovic Boudinet 

If you only have Sub-tasks in the structure and you want to extract values of their direct parents through the parent.some_value formula, then it depends on what type of a field you're trying to extract. If the field is too complex or it comes from another app, then it is possible that it's not exposed to the Formula to access through the parent function. In this case, we recommend to add parent issues to the structure, add their Sub-tasks under them with the Sub-tasks Extend generator and show the parent value either in the field-based column, or by using the parent{abc_no} aggregate function.

I hope this helps. If you need further assistance or have other questions about Structure, please contact us directly at our support portal and we'll get back to you shortly.

Best regards,
Stepan
Tempo (the Structure app vendor)

[Ludovic Boudinet]

thanks for your reply.

Unfortunately, it will not serve my purpose to add the parent JIRA in the structure.

This custom field is of a type "text" and should in theory (at least to my understanding) be extractable.

The issue seems to be really about the syntax and how to use custom field using space and dot when trying to read parent information. If there is a solution or trick to do it, I'd prefer such solution.

I tried:

• var1."ABC no."
• var1.ABC_no (because it's written somewhere to replace space with _ and remove special characters for custom fields)

(at the moment I'm evaluating with my JIRA admin to rename this field to remove space and dot but it's a shame as it's used by many teams).

[Ludovic Boudinet]

actually, after further testing it seems not working at all to get custom fields this way.