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

Automation ignoring field that DOES NOT exist

Kristen Fiore_5tg90r

Hi all,

I'm working to create automated onboarding tasks that create as new issues once an onboarding issue is submitted.

Every error on the automation notes it is ignoring a field that doesn't exist?

Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -Parent (parent)

But also, I am not a developer and I don't know what the hell I am doing. My IT team doesn't really have time to help me with this implementation and I am losing my mind. Is this related to the fact that I am creating issues in an automation?

This is my janky rule. Please keep the laughter to a minimum. I thought perhaps the issue was that I was trying to modify the linked issues field in the issue type so deleted that and created a branch rule to link the trigger issue to the last created ticket. Which is a disaster.. and did not fix the problem. I plan to delete that since editing the linked issue field linked the issue together the way I wanted.

rule issue.JPG

Please put me out of my misery!

Accepted answers

All comments

Olga Videc

Hello @Kristen Fiore

Np, the community is here to help.

Can you explain in little more detail what are you trying to achieve?

When an onboarding issue is created you want to create tasks for onboarding?

Okay is onboarding issue and tasks in the same project? Do you want to add tasks as sub-tasks to the onboarding issue?

If you can write step by step what you want to achieve.

BR, Olga

Kristen Fiore_5tg90r

Thanks, Olga.

The goal is that when a customer uses our onboarding form that new issues are created with specific summaries and assignees. These are triaged in each department that needs to handle their onboarding - admin, technology, and operations.

We were creating subtasks, but that didn't allow us the flexibility of a full issue type as we have to interact with the employee and their supervisor for various tasks.

I'm technically fine with the error message, as it is doing EVERYTHING else I need it to do, but the parent field does not exist in any of our field configurations so I am super frustrated.

Ayal Kellman

I have the exact same issue with a rule I just added.

Could it be because we first added the rules to add subtasks and later edited the rule to add a new issue a different project? Perhaps there is some code there still looking to attach it a parent issue?

Olga Videc

Hello @Kristen Fiore ,

I think the error occurs in the last part "for the most recent created " because you want to link to an issue that hasn't even created or it's in creating mode.

First don't worry about your rule, especially if this is the first time doing automation, practice makes perfect.

Here is how you link the issue, so you can remove the last step.

In the create a new part, under "choose fields to set" choose linked issue - and choose trigger issue.

Automation 1.PNG

Please don't look at the error at the top, used automation playground to create this screenshot

BR, Olga

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management