Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automation error question. Check your custom field configuration. Fields ignored - Parent (parent)

I am using Jira Automation to create an issue on a separate project whenever a certain request type is generated on my Jira Service Management project. The issue type on the separate project is assigned the exact same screens/scheme as the request type that copies fields to it.

It creates the issue, but throws the attached error every time. I've been unable to find what this field is. Any ideas?jira_automation.JPG

1 answer

Hi @Logan Francis -- Welcome to the Atlassian Community!

Would you please post an image of your rule?  That will provide some context for the community to supply ideas.

Without seeing the rule yet, I wonder if one or more of the fields you are setting in the newly created issue, perhaps copying from values in the triggering issue, have different values or are impacted by workflow in the target project.


Best regards,

Bill

Sorry! There it is.. It isn't anything too complex, still new to this. All the fields it's copying are present on the issue type its copying to just in a different project.

Thanks, Logan.

Did you check if there any workflow restrictions/rules on the target project?

Also, this appears to be copying data from one custom sub-task type to another custom sub-task type.  Is that correct?  And if so, which issue is the Parent of the newly created issue, as that could be where the error message is coming from.

It's a template project I made for testing this action with pretty much nothing in it that I could tell would cause this no rules made at all within it. It's copying data from one custom issue type to another custom issue type named "Task" no sub-tasks. And I made both issue types pretty generic nothing special on them. They are assigned the exact same screen scheme as well.

Hmmm... that is curious.  The icon for both the trigger and new issue types looks like they are sub-task types, which I why I thought there was a parent error.

Do you have any workflow rules?

Ahhh yes I manually set that picture. I changed it now to be less confusing. No workflow rules at all. I even tried setting it to the same workflow in both projects, but the error persists.

Thanks for clarifying that!  The only time I have seen that error for automation was when the created issue changed/set a field which was not visible on the views, or a permission error for the field and the Automation user.  As you are not changing the parent that seems unlikely for this case, but could be worth checking for the other fields.

Otherwise, I suggest submitting a defect to Atlassian at the link below.  You should be able to do that as site admin for a paid license.

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

Like Logan Francis likes this

FYI for the possible permissions cause, there is a documentation page for Server that recommends using the guided "Where's my field" technique to try to solve it.  That should be the same approach for Cloud version.

https://confluence.atlassian.com/automation/solve-unknown-fields-error-in-the-audit-log-993924707.html

I will have a look thank you! Although I'm not sure how that could be since the assigned screens to both issue types are identical, but I'm also not sure what it means by parent(parent) though as far as a field goes for that.. especially when there isn't a parent associated with any of this.. it's a very strange one.

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you