Hi @Allie Hittner and welcome to the Community!
As you already describe: many teams have their own projects where they manage their work. HR is indeed typically a place where work for other teams originates (when new employees must be onboarded, transfer to a different department, ...).
It is usually best to support the already practices already used by existing teams. Adding sub-tasks in your HR project creates permission challenges there. So, because of that and because people usually already have ways of working within their teams, it makes more sense to create issues for other teams in the projects they already use. Linking them to the original request in the HR project creates overview on that linked work from the HR side of things.
Automation allows you to copy over any fields you need in these linked issues, as long as you make sure that information is already available in the HR issue when you create them. Building a consistent process comes done to a proper analysis of who is involved, what information they need, where people are working, what process each team follows and how teams' work influences the jobs of other teams.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.