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

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?

Accepted answers

Andy Heinzer

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

All comments

Trudy P 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

production rule.png

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

Andy Heinzer

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

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.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

atl-rvw