There is a code example here for getting the two parts of a cascading select:
Personally I'd consider solving this problem with an excel macro rather than redundantly storing both parts separately.
The only solution I know of is to write a pair of custom fields (derived custom fields, so nothing extra in the database), that pull their values from the parent and child separately. They'd effectively be read-only select lists. You could also do it with a single one by concatenating the cascading values, but that breaks the reporting in some ways because it flattens the cascading select (e.g. if you've got A-aaa, B-aaa, and C-bbb as your three cascading select values, then you can't report on "where second layer is aaa". You can if you have two fields)
Leave them off screens as you don't need their values repeated. I'm pretty sure the script-runner will let you do these fields without having to write a plugin.
Like Jamie, I should have pointed out it's a bit of overkill to expose it as fields. I've given a technical answer without looking at the wider problem again.
I agree with Jamie - step back and look at the requirements. My fix is generalised, but if you've only got one or two specific reports/questions, then it would be better to code directly for them.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs