Custom cascading fields coming as Json String when I am exporting to Excel all issue fields.
Y
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.
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"
Kavitha Vaikunthavasan
Hi Yash,
we are pleased to announce that the CSV export issue has been successfully resolved in our latest update.
Best Regards,
Kavitha
P.S. If our app has been beneficial to you, we would greatly appreciate it if you could take a moment to leave us a brief review.: https://seibert.biz/acf-jira-review
Paul Pasler
Thanks for your post!
I just talked to Atlassian and they justify the behaviour with problems when importing Excel files back to Jira. But they'll might solve this in the future.
This is the (technical) issue in the Atlassian ecosystem: https://ecosystem.atlassian.net/browse/FRGE-1127
We'll keep you up to date if anything happens :)