Create subtasks across team-managed projects using a single, global automation rule

Carina Lora

My org uses team-managed projects so various teams to customize issues and workflow. However, all teams want and need the ability to request feedback on their work. We currently have a global custom field "reviewers" for the reporter to specify users who should monitor the work. Each project has an automation rule to assign separate "Review XX" subtasks to each {{reviewer}} user on a given transition. This works well, except for the administrative overhead of ensuring consistency across 30+ separate rules.

I would prefer a single global rule that applies to all projects, but the team-managed projects have distinct issuetype.id for subtasks in each project resulting in an invalid issue type error.

I've tried to lookup the subtask issuetype.id to then set as part of the automation, or set hierarchy=-1 , but neither have worked. 

 

Bill Sheboy

Hi @Carina Lora 

I recall some open suggestions about such needs, and those no doubt led to the recent feature to share global (i.e., company-managed) fields with team-managed projects.  But that does not help for issue types...

One possible workaround is to not use the Create Issue action in your global scope rule.  Instead use the Send Web Request action to call the REST API endpoint to get the issue type's id for the specific project, and then use another call to the REST API to create the issue with that id for the type.

If you want to try this approach, here is a how-to article for calling the REST API from a rule, and the links to the needed endpoints' documentation:

• how-to article: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828
• get the issue type data for the project: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-createmeta-projectidorkey-issuetypes-get
• create the issue: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-post

Kind regards,
Bill