Parent field mandatory validator error

[Cindy Kim]

My company has been using Validator in the workflow to require the Parent field when creating an issue for over a year.

However, the parent required error kept appearing yesterday out of no clue, even though the parent field was filled, so my whole organization members couldn't create any issues. 

We didn't change any settings, so I rolled back the workflow and tried to set it again, but the same error occurred, which seems to be a critical bug in Jira.

Making the parent field mandatory is essential for my company to keep track of the resources. And as you may already know it can't be set as required like other custom fields do since it's a default field provided by Jira.

Does anybody have a clue on this issue?

[John Funk]

Hi Cindy,

Did you try creating an issue without the workflow having the validator set? Just to verify it's the validator doing it. 

If so, you probably want to report as a bug if it is still happening. 

https://support.atlassian.com/contact/#/

[David Nickell]

Let me start by saying "I do not have an answer -- only some intuition"

Are we talking about PARENT or PARENT LINK?  I am also showing EPIC LINK below because that is how old school I am:

Since the Parent Field is engrained in JIRA as you mention, I wonder if this check box on the CREATE transition validator is a factor:

The other thing I hate to even mention because it's from my experiences MANY years ago, but do we have a timing issue here?  Does the field truly exist at the time the issue is being validated.  That is to say, does the issue have to be saved 1st?  (the CREATE is a POST Function which happens after the Validator).

Also -- if ChatGPT is correct, the PARENT field connects Parent-Child relationships like subtasks.

PARENT LINK is an optional field tied to Jira Portfolio Object, which is related to Advanced Roadmap with the hierarchy field for Issue Types.   

I don't recall asking users to populate a PARENT field in the past for subtasks.  That connection was always automatic

Hope this helps and ends up being somewhat relevant :-)

[Trudy Claspill]

@David Nickell 

The poster indicated they are using Jira Cloud. In that product all parent/child relationships at all levels now use the Parent field. Atlassian made this change a year or so ago.Parent Link and Epic Link are deprecated.

[Trudy Claspill]

Hello @Cindy Kim 

Can you provide a screen image showing the Validator configuration?

Are there any other validators on that transition?

Can you show an example image, showing the Parent field, where the transition failed?

Is this for a Team Managed project or a Company Managed project?

[David Nickell]

Not to go too far off topic -- but your comment and questions are great!   I recently set up my first JSM Project and Portal and prompting users reporting bugs (or questions in this case) to provide the level of detail you mention is vital to investigating an issue.

That said -- maybe a "Form" like concept or "Template" can be adopted here to prompt our community for the information needed (in general).  

I don't even know if it is possible -- but your reply and my recent work set off a synapse or 2

[Cindy Kim]

Hi @Trudy Claspill 

we are using company-managed projects, and the validator was set as shown in the attached image. However, when I tested it again today, it seems to be working fine. Perhaps it was just an error that occurred yesterday and has since been resolved?

This was the image my team member sent me yesterday.

The error message appeared even though the parent field was filled.

Thanks by the way!