Hi there, let's see if anyone can help :) I already read this thread and didn't help. I'm trying to have a new issue created in another project upon assignment. * -Both projects are team-managed Business projects * -The other project is owned by the assignee I already tried changing the target Issue Type (ideally "same as trigger issue" but also chose "task") without success. Any ideas? Thanks!

You should probably deal with the Due Date in a separate step then. Leave it out of the Clone process. Then add a Condition where the Due Date is empty. Then add an action for Edit Issue and just use the due date field. Then copy it from the parent.

Hi! About the due date, I just didn't want it to be empty in the children issues. If the children issues don't have one, it's OK to inherit it from the parent issue (whether it's the original or this one, should be the same)

Sorry, missed the part about changing the trigger for the parent. So what doesn't work with the latest rule? Also, you can't use {{issue.duedate}} for the Due date because that is the same issue. If that should be the same as the one you are cloning from, you don't need to add that field. If it is set from something else, what is it?

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 Failing: Cloning an issue to another board upon Assignment

Marta_rab97q

Hi there,

let's see if anyone can help

I already read this thread and didn't help.

I'm trying to have a new issue created in another project upon assignment.

-Both projects are team-managed Business projects
-The other project is owned by the assignee

I already tried changing the target Issue Type (ideally "same as trigger issue" but also chose "task") without success.

Any ideas?

Thanks!

Accepted answers

All comments

John Funk

Hi Marta,

Team-managed projects are totally independent of each other. So when you say same as trigger issue, it doesn't really know what that means in this case.

So, you need to actually select a value for the Issue Type. If that doesn't work for some reason, then try to do a Create new issue action instead of Clone issue.

Marta_rab97q

Thank you so much, John! Sorry I forgot to attach the screenshots!

Screen Shot 2024-05-08 at 17.51.41.png

I got this type of error both before and after changing to a specific Issue

John Funk

Can you share the details of the Clone issue into: step?

Marta_rab97q

I've had these two options, as mentioned:

1) (I understand now why this would fail)

Screen Shot 2024-05-08 at 18.24.27.png

2) I don't understand why this would fail

Screen Shot 2024-05-08 at 18.25.15.png

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-cloud

jira-service-management