Slack → Jira integration: Unable to create Task issue when setting Parent field via code value

Question

Details

We are currently using the Slack–Jira integration to create issues directly from Slack (mainly Task-type issues).

However, we are experiencing an issue with the Parent field:

* When creating a Task issue from Slack
* Even if we pass the Parent (e.g., Epic or parent issue) using its code/key value
* The issue creation does not complete successfully in Slack

In contrast, creating the same issue directly in Jira works without any problem.

Expected behavior

* When providing a valid Parent issue key (e.g., EPIC-123),
the Task issue should be created successfully and linked correctly.

Actual behavior

* Slack workflow fails to complete issue creation
* Error message indicates there is an issue with the provided data, but no clear detail is given

Additional context

* Issue type: Task
* Required fields: Only Summary (others are optional)
* Parent field is configured and works properly within Jira UI
* This issue occurs specifically when creating issues via Slack workflow

Why this matters

Our team frequently creates Task issues from Slack for quick workflows,
so resolving this issue would significantly improve productivity.

씨엘 · Answer

Thanks again for the reply, Tobi!

We checked our Jira configuration again, and the Parent field is currently optional, so it does not appear to be a workflow validation issue.

We also confirmed:
- Creating the same issue directly in Jira works correctly
- The issue only occurs through the Slack workflow integration

Additionally, after further testing, we found that:
- Even without the Parent field, issue creation sometimes still fails
- The problem now seems to occur whenever creating Bug-type issues through the Slack workflow

At this point, it looks more like a Slack ↔ Jira integration issue rather than a Jira workflow configuration problem.

We already contacted Slack support as well, although we suspect they may redirect us to Atlassian support.

If we find any workaround or root cause, I’ll share an update here.

Thanks!

Tomislav Tobijas · Answer

Hey @씨엘 ,

I think I've heard it once or twice that there are some issues with this integration, especially after Atlassian moved from using Epic Link to Parent field. You could check the workflow if it's potentially enforcing Parent to be mandatory, but as you said... that might not be it (as it's currently set to optional) 🤔

I've tried searching for feature requests or bugs on that topic, but couldn't find anything 👀

Have you maybe tried reaching out to Atlassian Support to see what their team has to say about it?

Cheers,
Tobi