Need a jira automation rule to move tickets from JSM project to Jira SW project as they get created

[Heba Rezk]

I have one JSM project where i receive requests coming from different teams, and another Jira SW project where the engineering team add subtasks to each request to execute, i tried to clone the ticket from JSM project to Jira SW one (due to limitation on JSM licenses) but not all fields get copied to the destination Jira SW one (though i use the same field and issue schemes) however, when i moved tickets one by one, all fields were copied in the destination project. any help on what is going on?

[Syed Majid Hassan -Exalate-]

HI @Heba Rezk

This is Majid @ Exalate. 

What fields do not get copied over? Maybe you can write a small automation but I do not think you should need it to be honest. You can also explore the possibility of outsourcing this integration work to an app like Exalate - and control the sync from the "back end".

Hope it helps.

Thanks

Majid

[Luka Hummel - codefortynine]

Hi @Heba Rezk

I'm Luka from codefortynine and escalating support requests is actually a really common use case for our Deep Clone for Jira app. My colleague @Marlene Kegel - codefortynine even wrote an excellent community article on the use case.

To quickly escalate an issue, you can create a preset and link that issue to the Actions menu •••.

[Thibaut Subra _Elements_]

Hello @Heba Rezk 

As your need is pretty common, we developed an app called Copy & Sync that can help you to copy and synchronize tickets from a JSM project to a JS one.

If you can tell us more about your triggers and how exactly do you copy your issues from one project to another, we'll be glad to help you. In the mean time, you can take a look at an example of an escalation process we have set up.

In your case, after setting your Automation rule, save time and effort and just trigger your recipe using our API. That way, you can easily adjust your recipe depending on your current needs and be more granular.

Let us know!

Regards

Thibaut

[Ste Wright]

Hi @Heba Rezk 

Could you provide more details about your current rule?

Ste

[Heba Rezk]

I clone all fields i need including "request type" (this one does not get cloned) it always comes empty and i can not access its options. I made sure that i have the same field scheme between JSM and Jira sw projects, but to clarify, the Request type field is set from the JSM project UI, where i edit request types those will be displayed to users in the web form.

[Ste Wright]

Hi @Heba Rezk 

There's no Request Type field in Jira Software, so the field won't come across.

Could you move it to another field potentially? Such as a select list field (and populating using smart values and/or IF/ELSE statements)?

Ste

[bduncan]

Not sure if this is your issue, but in the automation you need to specify each field for the clone mapping: