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; } } }

JQL for custom field to identify empty values

davide.lora

In our Jira Cloud instance, we have a custom field called "Parent Link" which allows to set another Jira issue as a parent issue.

I am trying to create a JQL for my project where I can identify all issues that do not have a "Parent Link" set.

My JQL looks something like this:
project = "myproject" AND issuetype = Epic AND "Parent Link" is EMPTY

I tried "IS EMPTY", "= Null" and multiple other variations but the query does not seem to work. Is there a solution to this?

Accepted answers

Brant Schroeder

@davide.lora

What type of custom field is it? What type of project teams or company managed? If you give me that information I can try and recreate the issue.

All comments

Brant Schroeder

@davide.lora

What type of custom field is it? What type of project teams or company managed? If you give me that information I can try and recreate the issue.

davide.lora

Hi Brant, thanks for your support.
The field is an issue link type of field (i.e. I can select a Jira ticket in the same project and set it as a Parent Link. Normally my issue is an EPIC and the parent is an INITIATIVE which is a custom Issue type).

The Jira instance is company managed but I can access the project settings.

davide.lora

I just discovered that "Parent Link" might not be our custom field but a new field that was created automatically when our instance was upgraded to Jira Advanced Roadmaps.

To my understanding, we need to populate this field in order to fully show the hierarchy in Advanced Roadmaps

Dave

@davide.lora That's correct - Parent Link is a field provided by Advanced Roadmaps. In order to set it to a value you will need to configure additional hierarchy levels in the global Advanced Roadmaps configuration (see Plans -> Settings -> Hierarchy Configuration). As well as creating the hierarchy levels you'll need to make sure that you issue types assigned to the additional levels and that they are associated with the projects that you want to use them in.

Regards,

Dave

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud