How to clone JWM to JSM and set request type

[Glen Cochrane]

I have a JSM and JWM which clone issues to each other.

Each project shares the same schemes completely (issue type; workflow; etc).

Each issue type in JSM has only one request type.

When I create a JWM issue it clones as expected but I cannot figure out how to get the automation to set the JSM request type upon create.

Help - and thanks,
Glen

[Mikael Sandberg · Accepted solution]

To set the request type you can do it using the most recently created issue branch like this:

Since you said you only have a single request type associated with the issue your other option would be to use the default request type feature instead and not set the request type in the automation. 

[Trudy Claspill]

Adding to this...

The Request Type can be set only with the Edit Request Type action after the issue has been created/cloned. You can't set it as part of the Create Issue or Clone Issue actions.

[Glen Cochrane]

Hello @Mikael Sandberg 

Thank you for the reply. Unfortunately, I think these don't apply to my dilemma.

The default request type feature only works if an issue type is changed. I have this feature toggle turned on. However, since I am creating a JSM clone from a JWM, this is a create function not a change.

I think your automation example above is creating a clone or issue in a JWM project.

My particular scenario is to Create an (clone) issue in a JSM project from a JWM project; when a JWM issue is created.

I need the request type set upon creation of JSM Clone so the Reporter designated receives a New Issue notification email (as a customer of the request type).

[Glen Cochrane]

@Trudy Claspill thank you.

I was wondering if this would be the case.

I guess I will have to add another rule to send the new issue email notification to the reporter, after the issue is created upon edit of the request type 😞

Unless you have another idea for this?

Cheers,
Glen

[Mikael Sandberg]

No, the screenshot I included is creating a task in a JSM project, but as you can see and like Trudy mentioned, the editing of the request type happens after the issue is created. That is what the Most recently created issue branch is all for. So the automation first creates the issue, then the branch will open that issue and then edit the request type.