Is there something on the roadmap for managers/leads of Teams and/or how are other users using this?

[#1]

We are looking into replacing several 'team-solutions' by the Teams function that Atlassian introduced. We really like the steps up until now, so thanks for that!

What seems to be missing for the more classic customers of ours is assigned a Teamlead/manager/product owner and surfacing that data in automation rules as well. This can be used for triaging, intake, and as addition; knowing who you would have contact for questions.

I looked through the discussion, but I could not find anything. How are others working with this?

And, @April Chi , is there something on the roadmap for this perhaps?

[James Rickards _SN_]

If you happen to be using Microsoft Entra for your IDAM and leverage office365 groups/Microsoft Teams, you can sync the `members` and `owners` groups separately. This has the added benefit of having self-managed membership.  Link the Member group to an Atlassian team, but reserve the owners group for automations.

[Jeremy Evans]

Hi @Edwin Stol ,

We do have something on the roadmap around Custom Fields for teams. These will allow user defined fields and values per team, and eg could be used to create a "Team Lead" field that takes an accountId.

Right now there is no direct integration with automation rules, but that is something we will certainly explore.

Hope that helps!

[Rune Rasmussen]

As I recall from previous posts the ability to have a "Team Owner", or something of that nature, was being considered but wasn't on the backlog.

And from looking at various suggestions in the Public Jira Board it looks like April is no longer with Atlassian.