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

How to clone an issue with different status?

Vladimir Sumilin

I'm not sure if I'm doing this right. So, I put when it should happen (Scheduled), then I put what should happen (Clone issue) and then I would like to have all my cloned issues the same status as NOT PASSED. I have attached the screenshot below, could you tell me if I am doing it right? I don't want to try it right now, because I have a lot of issues in my project and it will make a mess if I will make more tries

If I am doing this wrong, then how to connect this transaction which will say to all my issues that they should have the status: NOT PASSED.

Do I need to switch the Clone issue and Transition issue?

Thank you in advance!

Best regards,

Vladimir

Accepted answers

All comments

David A_s1ayjk

HI Vladimir,

I think now this automation clones all the tickets in your project.

I think you could add a condition after the scheduler where you jql indicate which issues you want to clone.

In this example only clone issues in status=blocked

Hope this helps!

Vladimir Sumilin

Thanks for your reply, but my problem is that I have specific status right now for all my issues and I would like to have a different one for all issues which will be created after 11 months.

Right now I have all issues status as "Passed" and would like to create with automation the next ones with the status "Not Passed".

Nic Brough -Adaptavist-

The clone process just clones the issue. It can't change any of the data on it, it wouldn't be a clone if you did.

There are some apps that do enhanced cloning, which may suit you in this case.

If you want to do it in an automation, you are going to need a new chunk of automation steps - retrieve the new issue and update it as necessary (you might add that to the end of your current one, or have a second one for "when issue cloned, with the new one...")

Vladimir Sumilin

Hi Nic,

Thanks for your reply. My idea was that I will clone the issue and then Transition the issue to "Not Passed".

I just wanted to make the status for cloning by default - Open/Not passed. Maybe it's not possible to do it in Jira then.

Nic Brough -Adaptavist-

Um, have another read of my last paragraph!

The thing Automation can't do is move issues to other projects (because it always needs humans to do it)

Vladimir Sumilin

In my case it should be the same project, I'm not moving my issues to another project

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