Original ticket: https://ecosystem.atlassian.net/browse/ACJIRA-2735

Dear Atlassian Team,

The parent field has been available in Jira Expressions for some time. It was introduced to replace the epic field and to provide a unified way of handling issue hierarchies across all levels, ensuring consistency when working with parent-child relationships in different issue types.

However, according to the documentation:

The issue parent. During issue creation, only available in workflow validators for subtasks in company-managed projects. It's available for all existing issues.

The parent field is still not available during Issue Create for all hierarchy levels in Jira - those above Epic, added in Jira Premium (it is always null in Jira expression). While there is a workaround using the epic field for Stories/Tasks under an Epic, there is no similar workaround for higher-level issue types like Initiatives.

Users of our app, have been requesting a Workflow Validator that would prevent the creation of child issues if the parent issue is already closed. This feature would help ensure that closed parent issues don’t end up with new, unresolved child issues. The request is specifically aimed at Jira Premium users, who utilize higher-level issue types in their hierarchy. It is already possible with custom (Jira expression-based) validators for regular transitions. The last missing piece is support for the Issue Create context

Current workaround for lower levels:

let parentIssue = issue.epic || issue.parent;

parentIssue
  ? ['new','indeterminate'].includes(parentIssue.status.category.key)
  : true 

However, this solution won't work for Initiatives, Legends, or other higher-level issue types used by Premium users.