Custom cascading fields coming as Json String when I am exporting to Excel all issue fields.

[Yash Limbachiya]

Due to only 2 levels of default cascading fields we can create in Jira, I have installed the third party plugin named "Awesome custom fields" and I have create 3 levels of cascading fields for my company's purpose. But when I tried to export all the issue's fields to Excel then instead of normal text its coming as Json string. I have attached the SS for reference. 

  

and when I exported into Excel file its showing as :

{"selection":[{"id":"Option 1","name":"Manual Error","children":["Option 1.1","181977ec-fd8e-4a44-bfa7-015cc7d5f77f","10588de6-443e-4a10-96ec-e7042c3dfd5e"]},{"id":"Option 1.1","name":"Assembly Error","children":["b300dddd-8110-4c1e-836e-f11546a554a0","71e6d5fd-09cb-494c-90d2-8fad04ae6e3a","ea78d008-7586-4b34-a2c2-b19eaf842039"]},{"id":"ea78d008-7586-4b34-a2c2-b19eaf842039","name":"Component Missing - Final Assembly","children":[]}]}

Instead of "Mannual Error->Assembly Error-> Component Missing -> Final Assembly"

[Bill Sheboy · Accepted solution]

Hi @Yash Limbachiya -- Welcome to the Atlassian Community!

I recommend contacting the vendor of that marketplace addon to learn what they suggest.  If they do not have an answer you might try writing an Excel macro to parse that information.

Kind regards,
Bill

[Yash Limbachiya]

Hi @Bill Sheboy -- Thanks for your quick response!

A support ticket has already been submitted to the vendor of that marketplace, and I am awaiting a response from them. Although I have tried to vlookup that key value from the JSON, because there are multiple child values with the same Key it does not work and only gives me the value of the first key.

Highest regards,

Yash