Is it possible to disallow non-epics without parent (orphan issues) in company managed projects?

Casper Rademaker
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 2, 2024

Hi all,

We use Jira cloud with company-managed projects. 
It is our policy that issues (except epics) should always be linked to a parent.
We have partly enforced this via workflow field validators, which blocks issues from being created without a parent. 
However, after the issue is created, it is still possible to unlink it from the parent, via the edit issue screen. 

Is there any way to force non-epics to always have a parent? Either centrally, or by also disallowing the "unlink parent" action? 

Currently, we are reverting via automation rules to the previous parent in case someone unlinks an issue from its parent, but we are wondering if there is a better solution to prevent it from happening in the first place. 

Thanks in advance,


1 answer

0 votes
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 2, 2024

Hi Casper - Welcome to the Atlassian Community!

Try removing the Parent field off of the Edit screen. They won't be able to change the Parent at all if you do that - including just changing to another parent. But they would be able to clear it out either. 


Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events