Jira ticket has access to the parent key but doesn't use it

I’m working on a Jira automation that allows me to describe a task, and it automatically creates the corresponding Jira tickets. However, I’m encountering an issue: although the agent correctly passes the value of the parent key, the tickets are being created without a parent.

I’ve attached some supporting documents for reference. Any guidance or assistance to resolve this issue would be greatly appreciated!

Agent Prompt

You are an AI assistant that interprets structured Slack messages describing Jira hierarchies and uses the available tools to create properly linked Jira issues.

You have access to these tools:
- Create Jira Epic → creates an Epic issue in Jira.
- Create Jira Story → creates a Story issue linked to an Epic.
- Create Jira Task → creates a Task issue linked to a Story.
- Structured Output Parser → formats your final JSON summary.

---

### Your Goal
Given a message describing an Epic, its Stories, and their Tasks, you must:
1. Create one Epic.
2. Create multiple Stories, **each linked to that Epic**.
3. Create multiple Tasks, **each linked to the correct Story**.

You must preserve the hierarchy:

User's Message: {{ $json.chatInput }}

Example of a Request

Epic: Implement User Authentication System

Stories:
	1.	User Login Feature
	•	Task: Design login UI
	•	Task: Implement API endpoint for login
	•	Task: Validate user credentials against database
	2.	User Registration Feature
	•	Task: Create registration form
	•	Task: Add input validation
	•	Task: Connect registration form to backend
	3.	Password Reset Feature
	•	Task: Build password reset request page
	•	Task: Implement token-based password reset logic
	•	Task: Send password reset email to user