Getting (400) Bad Request when cloning issue using automation rule with manual trigger

[Nikki Colletti]

I am trying to use an automation rule that is pretty basic and using manual trigger.  The first step is an if condition that if a specific label does not exist to then clone into a different project.  I am passing this If condition, but then when trying to clone the issue to a different project I am getting (400) bad request message.  When cloning the issue, I have set to clone to a different issue type than the trigger issue type and into a different project.  I am only setting one field while cloning, and that is to create a linked issue to the trigger issue.  The project I am trying to clone into only has 3 statuses - ToDo, InProgress, and Done - the project I am cloning from has these same statuses, but also has about 10 other statuses.  

I have a group of test projects where I have enabled this rule, and it is working fine.  I am baffled as to why this same rule is failing in my other project.  Any ideas?

[Andy Heinzer · Accepted solution]

Hi @Nikki Colletti 

I created a support case for this on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-987751

I expect that our support team might want to request data access to review this specific project configuration and the automation setup to see if we can't narrow down why this error is being generated by automation.

Andy

[Nikki Colletti]

Thank you Andy - support team pointed out that the user that the original ticket was assigned to did not exist in the project I was trying to clone the case into.  I updated the rule to set the Assignee to unassigned when cloning into the new project, and that solved the issue. 

[Kevin Cinquegrani]

I am having the same isssue but I found a workaround.
Instead of cloning the issue I create a new one and initialize it with my needed parameters & Custom-Parameters.

[Trudy Claspill]

Hello @Nikki Colletti 

For the rule that is failing, did you build it from scratch or start by copying a different rule?

Sometimes rules get glitchy from undergoing a lot of modifications. Or if you started by copying another rule and changing it there could be something that didn't get fully changed over from the copy.

Try creating the rule from scratch and see if that new version of the rule works.

Otherwise, please show us the complete rule, details of each step in it, and the output in the Audit Log for its execution.

[Nikki Colletti]

Hi Trudy

Here is the rule I am trying to use followed by the error it is returning - this exact rule is working in my test projects

Action details:
Manual trigger
Nikki Colletti triggered the rule
Issue condition
The following issues passed:
DOC-11364
Clone issue
Error creating issue
Bad Request (400)
Edit issue
Issues edited successfully
DOC-11364
Associated items:
Manual trigger
DOC-11364

[Trudy Claspill]

I don't see anything obvious wrong with that.

Did you build it from scratch or start by copying a different rule? Have you made multiple edits to it?

If you did not create it from scratch, try recreating the rule from scratch and see if that new version of the rule works.

[Trudy Claspill]

I have just seen another post from another user getting the same error.

I am flagging both posts to be looked at by an Atlassian Team Member.

[Bill Sheboy]

Hi @Nikki Colletti 

Adding to Trudy's suggestions with some requests / questions...

• When did you notice this error: immediately after creating and using the rule, or did it start happening recently after the rule was working successfully?
• Would you please post images of both the audit log details showing the error and of the Clone Issue action?
• What types of projects are involved: company-managed, team-managed, one of each?
• Are these software, business, or JPD projects?

Kind regards,
Bill

[Nikki Colletti]

Hi Trudy and Bill

I created the rule from scratch.  I just deleted and created brand new from scratch.  We are using team managed projects (kanban).  I have the exact same scenario setup in a group of test projects that I use to test new automation rules, and it is working in the test project.  Initially when I set up the rule in this project it was done as an automation trigger based on transition of a status.  After turning on it was tested and it ran, there were two other successful runs, and then it started to fail without any changes being made.  I tried making a few changes and it still would not create the clone.  I then deleted the original rule and created one based on a manual trigger. This was first created in my test environment and it worked fine, but when I set up the same rule in our main project it failed to create the clone

[andrew.logan]

I'm also getting a 400 bad request when trying to create an issue through automation.

I've read some other queries with answers suggesting that there "may be other fields required to create the issue than you think, keep adding more fields", but surely cloning the issue straight up should work?

I've looked at permissions to create issues, but that seems all good. I've looked at creating the issue in another project without any required fields, no dice. I've also changed the "Actor" to me, no joy there either. I'm beginning to suspect there may be a bug with creating issues through automation.

[Kristine Lurane]

I'm getting the same error message, but the automation seems to have an issue with epics specifically. If there's no epic on the trigger issue, then it works fine.

I know Jira recently changed how epics/parent cards look - could it have something to do with that?

Will put this as a separate question if needed, but these all sounded similar to my issue.

[Rafael Matos]

I'm getting the same error message

[Ian Robinson]

This may be linked to an issue I am seeing, also getting a 400 bad request on create. the automation is straight forward, when Major Incident is toggled create an issue and link it.

[Benjamin Proctor]

Also am running into this error with multiple similar rules. Nothing suggested thus far in this thread has resolved; any further thoughts on a solution?

[John Holford]

I am also running into this issue. Fairly simple cloning rule that has been fine for weeks is now failing with (400) Bad Request. 

[Ian Robinson]

Hi,

I found the issue for myself, someone had set one of the custom fields which were getting set in the 'create issue' as 'required'

So I had to declare this specifically within the 'create issue' and COPY from source.

That stopped the 400 error I was seeing

[Benjamin Proctor]

@Andy Heinzer any other suggestions for the rest of us here running into this? These rules were working fine before April, was there a change on Jira end that could have affected automation rules such as these? Thanks!

[Andy Heinzer]

@Benjamin Proctor It's difficult to say.  This particular error is generic enough it doesn't tell us what exact field is the hang up.  But it does suffice to indicate that the system is unable to create the issue with the exact data supplied to it. 

I would recommend that you reach out to a site-admin and have them raise a support case so that our team can investigate this more closely.  It is possible there is something in the environment that has changed to cause this, but without a support ticket, it would just be speculation.

[Benjamin Proctor]

Got it, thanks @Andy Heinzer. I'm one of the admins on my end so if I still can't find a solution I'll open up a ticket. Just is odd that it was working before with no issues and no changes have been made.

[Andy Heinzer]

Hi @Benjamin Proctor 

You might be a project admin, but I'm afraid that to open a support ticket with us, your role on the site would have to be that of a site-admin or a billing/technical contact.  I have created a support case on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/59/CES-37140 and I have added someone from the site-admin role on your site.  In order for our support team to exam the specific automation rule, we would need the data access approval of a site-admin.

[Benjamin Proctor]

@Andy Heinzer Yes, I am a full site admin not just project admin. Thanks for creating the ticket, can work with y'all Friday to dive into this deeper.

[andrew.logan]

This ended up being a permissions issue - the project I was trying to create the issue from did not allow bots to create issues. The error message I was getting told the truth, it was a bad request!

After fixing that there were a couple of minor issues with mandatory fields which I managed to work through.