How can I clone Jira service management issues to Jira software project with attachements?

[Ignas Selvestravičius]

I have a problem with automated issue cloning from service management project to software project. I can clone every field except attachments. Any solutions or workarounds? 

The case: I want to use jira service management project to collect issues from employees that are roaming around the city and taking pictures. This job must be quick, like a few button clicks. For this I created service project request form; in this way you can create issues within few seconds (faster than creating issues in jira app dircetly in a project, I tested it) and this is important. Then automation is triggered and issues are cloned to software project for further work (we can't let ourselves buy a bunch of agent licences just for the sake of this).

The problem: cloned issues does not have attachments. I have found that jira do not support attachment cloning directly. So maybe there are some workaround techniques?

This is important: cloning should be automated, but if there is a solution without automation, I might use it if it works

[Marlene Kegel - codefortynine · Accepted solution]

Hi @Ignas Selvestravičius,

I am Marlene from codefortynine.

With our app Deep Clone for Jira you can clone and move issues with attachments. It is also possible to automate cloning, by adding a Deep Clone post-function.

If you don't want to change the status to trigger a clone, you can work with looping transitions.

If you have further questions about Deep Clone, don't hesitate to contact our support.

[Ignas Selvestravičius]

Thank you, deep cloning worked for our problem. Works like a charm.

[Ignas Selvestravičius]

@Marlene Kegel - codefortynine  I have questions now :D I ran into a problem that automation cannot be trigerred by simple customers, only by agents :( thats a big problem for us. In automation log I got an error "Actor does not have permission to view one or more issues, or the issue was deleted (please check permissions and issue security levels)" whenever simple customer, not a project agent, is creating a request, so issue is not cloned. 

I dont know where should I look to change the right permissions, because Deep Clone for Jira - Bulk Clone and Deep Clone for Jira - Single/Epic Clone are granted "Public, anyone on the internet, including logged in and anonymous users" permission but automation rule still does not run automaticaly. Hovewer, it is possible to triger cloning rule in the customer portal with a button, but it's not very convenient to do 20-80 times per day.

In other words: requests are created by simple jira users (or anyone on the web, even anonimous users), not agents, and these requests should be cloned to Jira software project for further work.

[Ignas Selvestravičius]

I have already resolved this. Not related to Deep Clone app. The issue was related to Automation Actor so I changed it to "Automation for Jira" and then automation trigers without a problem.

[Marlene Kegel - codefortynine]

Hello @Ignas Selvestravičius,

Sorry for my late reply. I wasn't at work due to Easter holidays.

I am very happy to read that you were able to solve your problem. If you have any further questions or feedback, let me know.

[Vilmos Varszegi]

Hi @Marlene Kegel - codefortynine 

i want to deep clone from a jira software project to a servicemanagement project.
In which clone step can I select the project type?

many thanks
Vilmos

[Marlene Kegel - codefortynine]

Welcome to the community, @Vilmos Varszegi . And sorry for my late reply, I was again on vacation :) If you don't get a reply from me in the community, you can also reach out to our support team. They'll reply within one working day. 

You can select the "target project" within the Deep Clone dialog. In the target project you have a list of all projects you can clone into. 

If your project isn't listed, you might not have the permission to clone into the project. We only show target projects for which you have the "Create issue" permission, and that are not excluded by “Restrict Access” in the Deep Clone settings.

[Vilmos Varszegi]

Many thanks for the support.
Cloning with different project types worked.
The addon is really a great help.

[Marlene Kegel - codefortynine]

It's great to hear that. Thank you for the positive feedback. 

[Mathieu Lepoutre _Exalate_]

Hi @Ignas Selvestravičius 

I'm working as a pre-sales engineer with Exalate.

Automatically cloning issues to another instance with every field attached you so please, is the bread and butter of sExalate.

The ticket/epic/story (any type) will out-of-the-box be fully bi-directionally syncronized, which means, if a field gets updated on either side, it will automatically update on the other side, you can change this to make it uni-directional if you so please.

Exalate is easy and straightforward to set-up and you can control exactly which data you want to send and/or receive. 

If you would like to see a customized demo of the product, please book a slot with us. 

Cheers

Mathieu Lepoutre