Cross-project Automation for Request Type (JQL requesttype)

[JD]

Hi,

I want to develop a cross project automation where once an initiative is created in a Software project, if specific criteria are fulfilled, it will generate a story in a Service project. However, in this Service project, 'Request type' is required and the automation isn't able to generate because I'm not able to select the 'Request type.' 

Are there any workarounds/solutions? Cross-project automation is enabled and this same automation has worked between Software projects. Thanks so much! 

[Bill Sheboy]

Hi @JD 

Which rule action are you using to create the issue?

Have you tried Create Issue with Request Type?  Or perhaps try Create Incident.

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

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-incident

Kind regards,
Bill

[JD]

Thanks Bill! For some reason, I'm not able to find the "Create Issue with Request Type" action... Is this something that needs to be enabled?

[Bill Sheboy]

Do you have JSM permissions?  As a Site / Org admin for my site, I can see both actions in the rule editor from JSM and Software projects.

Please post an image showing what you see when you select adding a rule component / action, and have selected All Actions.

[JD]

Thanks Bill! Looks like I do not... I am listed as an Admin though but I will check with the Owner. Here is what it looks like on my end:

[JD]

Would you be able to share what you see @Bill Sheboy

Just want to make sure I have something to show the Owner in the unlikely scenario it's not there for them either. Thank you in advance!

[Bill Sheboy]

My understanding is the rule editor has improved over time such that it now accounts for scope, permissions, and what is possible at a specific point in a rule's steps.

This is what I see with a global scope rule, which can be adjusted to be just your specific JSM and SW projects' scope.

[JD]

Thank you! To confirm, this can be done in a separate project from the trigger? E.g. the issue is created in a software project called "ASAP" and when an issue in ASAP is created and the Environment = Beta, it will generate a new story in the Service Project "BETA" and be able to determine this story's request type:

[Bill Sheboy]

If the rule scope includes the service project and the actor has permissions, the action should be visible for use.