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?
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.
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.
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.
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.
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.
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