How to best collaborate between teams and between projects?

Allie Hittner
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 12, 2024

Our HR team often gets issues that gets issues, subtasks, or info that needs to be shared across to our accounting or IT teams in their own project instances. What is the best way to make sure that we can share those across without status issues, visibility/compliance issues, or using request participants?

1 answer

1 vote
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 12, 2024

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!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events