How to make 'Parent' field required/mandatory on the issue create screen in Co-Managed project

[Sophie Wright]

If I understand right, Epic Link has been replaced by 'Parent'.  I want to make 'Parent' a required field when creating a task & sub-task.  My 'Parent' are created as 'Epics'.  I can find this article How to make the Epic Link field required/mandatory on the issue create screen in company-managed projects | Atlassian Cloud | Atlassian Documentation - and have replaced 'Epic Link' field in my workflow validator with 'Parent' (and re-published the workflow) but the task is still able to create without forcing completion of the 'Parent' field. 

Any idea what I'm doing wrong!

[Trudy Claspill · Accepted solution]

@Sophie Wright 

Can you provide a screen image of the Validator you set up for the Parent field?

Are you sure you set that in the Create transition, in the workflow that applies to your issue type (Task)?

Is the Parent field included on the Create Issue screen associated with your Task issue type?

@Nic Brough -Adaptavist- , the second part of your answer is actually incorrect.

Jira Cloud has a native validator for Field Required, and you can select the Parent field within that Validator in a Company Managed project.

I added the Validator to my Create transition:

And  made sure that the Parent field is in the Create Issue dialog.

And when I try to create the associated issue without providing a value in the Parent field, I get an error:

[Nic Brough -Adaptavist-]

>"The second part of your answer is actually incorrect.

Jira Cloud has a native validator for Field Required, and you can select the Parent field within that Validator in a Company Managed project."

Yes, sorry.

I forgot that you have to switch to the old workflow editor to be able to use it. 

The new workflow editor does not have a rule for this.

[Trudy Claspill]

Oh, I haven't seen the new workflow editor in a Company Managed project. It would be unfortunate if the new editor doesn't provide access to the same Validators in Company Managed projects that are available in the original editor.

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

The "parent" of a sub-task is the issue of which it is a part.  A sub-task is always a fragment of an issue, it cannot have a different parent.

For issue-level items, you can not make the parent mandatory in the field configuration, so yes, a validator is needed if you want to do it.  But Cloud does not have a validator rule that can do that off-the-shelf.  You will need to find an app to do it.

[Lori Milam]

So, I have a request to require Parent only on Stories and Bugs. I have JMWE and I used that validator to put the condition on it. This worked a few days ago, but today it doesn't matter if you select a value for Parent or not you get the validation error. Here is my validator on the Create Transition.

Here is Parent on the screen.

[micagl admin]

I wonder why we have a field configuration for, if we cannot use it there... making it mandatory at all transitions and statuses is nonsense... means you will need the same workflow twice for different projects... What if you need to add another status? Or make major adaptations? You always need to do it twice or even more... and guess what, humans make errors... this is so error prone... Atlassian at its best.