Ticket cloning between project A, B and C

[Montnic]

Hi all! I am trying to clone a ticket from a Project A to a Project B and C. The cloning in project C works but for project B I get the red rectangle error. Can you help me? Thank you very much!

[Rilwan Ahmed]

Hi @Montnic ,

1. Check if you the automation user has all the required permissions to create ticket in project B
   
   
2. Check if reporter and assignee in A has all the required permissions (create ticket, browse project, assignable user, Assign issue) in Project B also. 

[Montnic]

Hi @Rilwan Ahmed 

Thank you for your response. Yes, I am an administrator so I appear in all projects.

[Rilwan Ahmed]

Hi @Montnic ,

It is not necessary that administrator has all the access in the project. Please go to project B settings --> Permission scheme and see the permissions. 

Also when you clone a ticket from project A, the assignee and the reporter are also copied from Project A to B. So these users should also have the permissions in project B. 

For further analysis, can you translate the error and send here. 

[Montnic]

Oh well, I'm seeing that the person assigned in A does not belong to project B. That could be the error then.

But if this is it, then I have another problem. If I just want to create a new ticket (i.e. change the action to create and not clone) I won't be able to bring the fields I mentioned when trying to clone the ticket.

My real problem is the following. I have a form in my project A but because it is not possible to insert the form in the cloning/creation of the ticket, I am creating custom fields so that when I call them in the cloning/creation they appear on the right side next to the details such as: priority, responsible, etc.

I hope I made myself clear

[Marc - Devoteam]

Hi @Montnic 

on the Clone action, choose what fields to set.

You could set the assignee field to unassigned for example

[Luka Hummel - codefortynine]

Hi @Montnic

I'm Luka from codefortynine 👋

I understand the frustration with encountering an error when trying to clone to Project B. If you are willing to use a third-party app, our Deep Clone for Jira could help you.

In this context, Deep Clone for Jira could be a highly effective solution. Deep Clone is designed to simplify and streamline the cloning process across different projects, handling various complexities and configurations.

Here’s how to clone an issue using Deep Clone:

1. Navigate to the issue you want to Single Clone

2. Click on the top right Actions menu ••• > Deep Clone

3. Configure and create your Single Clone