Manual automation rule to create a (linked) issue in another space

Question

Can anyone help me to create a manual automation rule. I want to create a linked issue in another space and set the right request type (work item type). I can create the issue but it doesn't seem to set the right work item, I used this:

{
"fields": {
"customfield_10010": "CR/509"
}
}

Bill Sheboy · Answer

Hi @Bianca de Weerd

Just following up to check if the suggestions from @Dirk Ronsmans answered your question.  If so, please consider marking this one as "answered".  That will help others with a similar need find solutions faster.  If not, please let the community know what help you need.

Thanks, and kind regards,
Bill

Dirk Ronsmans · Answer

Hi @Bianca de Weerd ,

I feel like you're making it more dificult than it should be. Which action are you using to create the new work item?

Are you cloning the trigger item or creating a new one and linking it afterwards?

Imho, the 2nd option (creating a new item and linking it) gives you the most flexibility.

A standard action exists for that too (with a request type or without):

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-work-item-with-a-request-type

Most of the fields should just be selectable and there is no need for adding it in JSON format. If you really want something a bit more exotic then you can indeed go to the "advanced" JSON option.

I would suggest:

* Create a global rule to make sure you can select different spaces
* Manual Trigger
* Create new work item 
* Branch on the "most recently created work item"
* Optional: update the new work item after creation if needed
* link both work items

Hari Krishna · Answer

In Jira Automation, setting the request type / work item type cannot be done by updating a custom field alone. The value you’re setting (customfield_10010) is just storing data, not defining the issue type.

To create a linked issue with the correct type in another project, you must explicitly set:

project

issuetype (work item type)

(For JSM) request type, if required

Example (Create issue action → Advanced / Additional fields):

{
"fields": {
"project": {
"key": "KEY"
},
"issuetype": {
"name": "Change Request"
},
"customfield_10010": "CR/509"
}
}

Notes:

The issue type must exist in the destination project

Request types are mapped to issue types in JSM, so once the correct issue type is set, the request type is applied automatically

You cannot change an issue’s type after creation using automation without Jira admin permissions