Current behavior
Board filter:
project = 'XYZ' AND "Cascading Field[Select List (cascading)]" IN cascadeOption("123", "456")
Steps:

• Configure a Select List (cascading) field Cascading Field with parent option 123 and child 456.
• Use the above filter on a company‑managed board.
• In the Backlog, create an issue via the inline “Create issue” button.
• Open the created issue.
   
  Result:
  Cascading Field has only the parent value set; the child is not populated
   

  ---

  Expected behavior
  When the board filter uses "<Cascading Field>" IN cascadeOption("parentId", "childId") (an unambiguous parent–child pair), inline issue create should auto‑populate both parent and child on the new issue so it fully matches the board filter.
   
  Impact/justification

• Teams rely on cascading fields and cascadeOption() in board filters.
• Only setting the parent forces users to manually pick the child for every backlog item, causing extra clicks and inconsistent data.
• Other select‑type fields are auto‑populated from board JQL; cascading fields should behave consistently when cascadeOption() clearly defines a single parent–child combination.