Hi Community! I am trying to make the Parent field mandatory when creating a ticket in a company-managed project. Current behavior: With the JMWE Field Required Validator, Jira shows “Parent is required” even when a parent has already been selected. With Jira’s default Field Required Validator, the issue can still be created without a parent. The validator is added to the Create transition. Is this a known limitation with the Parent field on the Create screen? What is the correct way to make Parent mandatory for the issue create screen?

Thank you all for your help and support. Your answers helped me better understand the issue and find a working solution. In my case, the solution was to use a ScriptRunner Behaviour for the specific project and work types where I wanted the Parent field to be mandatory. The Behaviour runs on the Create screen with the following script: const parentField = getFieldById ( "parent" ); parentField . setRequired( true ); This makes the Parent field required during issue creation for the selected mappings. I hope this helps anyone else who encounters the same issue. Thanks again for your guidance and for helping me find the solution.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Parent field validation does not work correctly on issue creation

David Shahbazyan

Hi Community!

I am trying to make the Parent field mandatory when creating a ticket in a company-managed project.

Current behavior:

With the JMWE Field Required Validator, Jira shows “Parent is required” even when a parent has already been selected.
With Jira’s default Field Required Validator, the issue can still be created without a parent.

The validator is added to the Create transition.

Is this a known limitation with the Parent field on the Create screen? What is the correct way to make Parent mandatory for the issue create screen?

Accepted answers

zoltanersek _outpostlabs_dev_

In company-managed projects, the Parent field only applies to issue types that actually support a parent (for example, Subtasks or, depending on your hierarchy configuration, child work types).

If you're trying to require Parent for a standard Story, Task, or Bug, Jira won't enforce it because those issue types aren't required to have a parent in the same way subtasks are.

If your goal is to ensure every Story is linked to an Epic (or another parent in the hierarchy), it may be worth clarifying which issue type you're validating and whether you're referring to the unified Parent field introduced in Cloud. That distinction can make a big difference in how validators behave.

David Shahbazyan

Thank you all for your help and support. Your answers helped me better understand the issue and find a working solution.

In my case, the solution was to use a ScriptRunner Behaviour for the specific project and work types where I wanted the Parent field to be mandatory.

The Behaviour runs on the Create screen with the following script:

<span>const</span> <span>parentField</span> <span>=</span> <span>getFieldById</span><span>(</span><span>"parent"</span><span>);
</span><span>parentField</span><span>.</span><span>setRequired(</span><span>true</span><span>);</span>

This makes the Parent field required during issue creation for the selected mappings.

I hope this helps anyone else who encounters the same issue.

Thanks again for your guidance and for helping me find the solution.

All comments

Fede Baronti -Deiser-

Hi @David Shahbazyan ,

Welcome to the Atlassian Community!

This is a limitation with the Parent field on the Create transition.

JMWE’s Field Required Validator does not really support the unified Parent field during issue creation, which is why it may still show that Parent is empty after a value is selected.

For this case I recommend to use Jira’s native Field Required Validator on the Create transition. And I would also recommend checking that

- the Parent field is on the Create screen

- That the validator is added to the workflow used by that issue type

- that the workflow draft is published (it is highly possible to miss this step)

If Jira still allows creation without a parent, double-check the workflow scheme and that you are testing the correct project and issue type.

Please note that this would be a Wokflow validation and not a field validation.

I hope this helps!!

Cheers,
Fede.

zoltanersek _outpostlabs_dev_

In company-managed projects, the Parent field only applies to issue types that actually support a parent (for example, Subtasks or, depending on your hierarchy configuration, child work types).

If you're trying to require Parent for a standard Story, Task, or Bug, Jira won't enforce it because those issue types aren't required to have a parent in the same way subtasks are.

Alex David_epseu5

Hey David, building on Fede's answer, here's the part that catches most people out.

The unified Parent field behaves differently from a normal field on the Create transition, so a 'Field required' validator on Create is unreliable for standard issue types. That's why you're seeing both symptoms at once: JMWE's validator misreads the unified Parent and throws a false 'Parent is required', while Jira's native validator lets the issue through without one. Hard parent enforcement at creation really only works for true sub-task types.

The route that actually holds is an Automation rule instead of a validator:

- Trigger: Issue created

- Condition: parent is empty (a smart-value condition checking {{issue.parent.key}} is empty works well), narrowed to the issue types you care about

- Action: depends how strict you want to be. Add a comment tagging the reporter to set a parent, move the issue to a 'Needs triage' status, or assign it back to the creator

It's a catch just after creation rather than a hard block on the Create screen, but for standard issue types it's the reliable native way to stop anything slipping through without a parent.

Hope that helps.

Alex

David Shahbazyan

Thank you all for your help and support. Your answers helped me better understand the issue and find a working solution.

In my case, the solution was to use a ScriptRunner Behaviour for the specific project and work types where I wanted the Parent field to be mandatory.

The Behaviour runs on the Create screen with the following script:

<span>const</span> <span>parentField</span> <span>=</span> <span>getFieldById</span><span>(</span><span>"parent"</span><span>);
</span><span>parentField</span><span>.</span><span>setRequired(</span><span>true</span><span>);</span>

This makes the Parent field required during issue creation for the selected mappings.

I hope this helps anyone else who encounters the same issue.

Thanks again for your guidance and for helping me find the solution.

Alex David_epseu5

Nice one, and thanks for coming back to post the actual solution. That's cleaner than what I suggested.

Behaviours run on the Create screen itself rather than at the workflow layer, which is exactly why setRequired works here when the validators didn't. Worth spelling out the difference for anyone finding this later: yours is a real block at creation, mine only catches it afterwards and tidies up. If you have ScriptRunner, yours is the better answer.

One correction to what I wrote, since I was too absolute. I said hard enforcement at creation only works for true sub-task types. That holds for native workflow validators, but not for Behaviours, and you've just shown the difference. The automation route is only worth reaching for if you don't have ScriptRunner or something similar.

Alex

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud