nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Changes to accessing Teams in Jira and Confluence

Ashwini Rattihalli

Hello everyone 👋,

I'm Ashwini, Product Manager for the Teams app, and I’m here to share an update about how you’ll access Teams across Atlassian apps.

What’s changing?

The teams feature is being relocated from Jira and Confluence. You'll be taken to the Teams app while accessing teams via the app shortcuts in the sidebar or through the app switcher.

Why are we making this change?

This change is part of our ongoing effort to make Atlassian apps more consistent and easier to use. By centralizing Teams in its own app, we’re simplifying navigation and making it easier to find and connect with your teams, no matter which Atlassian app you’re using.

What does this mean for you?

Rest assured, this transition will not affect how your users connect Teams to your work or alter any permissions you've set up. Teams will appear in the app shortcuts for users who previously did not see it in the navigation, but their permissions to use teams will not change.

When is this happening?

The rollout has already begun and will be available to all users over the next couple of weeks.

Jira before_after.png

Confluence before_after.png Teams in app switcher.png Teams landing page.png

Please feel free to reach out with any questions or feedback.

Cheers,
Ashwini

Comments

Rune Rasmussen

Decoupling Teams from the individual products is a good move I think.

What other things is in the pipeline for Teams?

Some things we need before we can really begin using Teams are:
Admin control over who can create new Teams - Otherwise it's just a matter of time before duplicate/wrong Teams gets created and then we'll have to keep cleaning that up.

General settings for who can manage a Team - Because Teams not linked to a group should be owned and managed by someone and not everyone.

Custom Teams fields (single and multi-picker) with the ability to scope which Teams can be selected (like we can on User picker fields). - because sometimes the Stakeholder is a team of people and not just individuals, and sometimes not every Team should be selectable.

Josh

I agree with @Run ; better RBAC for admins would be very helpful when it comes to Teams.

@ash one key missing piece of Teams functionality is the ability to limit a work item's assignee based on the selected team.

For example - the Server team is selected on a work item. We'd then want to limit the Assignee list to members of the Server team rather than every possible Jira user.
Ideally, this functionality would be configurable at the project level so some projects could have open assignments and others would be bound by team-based assignments, as needed.

If you'd ever like to discuss this use case more, I'd be happy to jump on a call.

Ashwini Rattihalli

Thank you for the feedback!

We’re currently planning improvements to admin controls for Teams. While we're still in the early exploration phase, we’d love to get your insights on the direction we’re heading.

@Rune Rasmussen – For the Team custom field type, could you please also upvote this ticket?

@Josh – That’s a great suggestion. I didn’t find any existing ticket for it. Could you please open a new one and include your use case?

I’d love to discuss your requirements and share more about the direction we’re exploring. Feel free to book time with me using this link to my schedule.

Rune Rasmussen

@Ashwini Rattihalli Thank you for pointing out that feature request.
I have voted for it.

I have booked a time slot with you this Friday, and forwarded it to my admin colleague as well.

Susan Hauth _Jira Queen_

Hi,

Makes sense that it becomes an App like "Assets".

Re: Teams. Is there any plans for some functionality like:

Add a Team as a watcher
@mention a team
Assign to a Team (via the Assignee)

Agree that we absolutely need some permissions on Teams otherwise it becomes the wild west and unusable.

Thanks,

Susan

Ashwini Rattihalli

We haven't considered that yet
We support @mentioning teams across our Apps. You can try this in any text field
Our current thinking is that the assignee should represent a single individual—someone who is clearly responsible for moving the work item forward. When a Team is set as the assignee, it often becomes unclear who’s actually accountable for progress. That said, I’d love to better understand your use case—could you share more about the scenario where assigning a team makes sense for you?

Rune Rasmussen

@Ashwini Rattihalli The @-mentioning Teams is not entirely amazing. It's quite clunky looking.

If we go by your "Magnetic IT" example it would look something like this:
Magnetic IT(@first member @second member @third member and so on...)

So if you're mentioning a large team it suddenly takes up a significant amount of space in your text.
It seems like it's not so much a true mention of the Team but more of a shortcut to individually mention all team members.

Susan Hauth _Jira Queen_

Hi,

What about adding Teams to watchers? Or being able to notify Teams in automation?

Susan

Cornelia Jeppsson

Hi! Having it as a separate app for Teams is not a bad idea I guess and especially if this means you will be able to add more control over who can create teams, BUT it was so much smoother to manage Teams in Jira before this change as you would not need to leave Jira to make changes - is it possible to embed it into the Jira UI instead of always leaving the Jira app when opening Teams from there? I would like to be able to use the teams functionality without leaving Jira like before. Now I have to open a separate tab and the feeling is just that it is a bit more cumbersome to reach it.

Just like confluence pages now open up inside jira when opening a link from there, it would be super convenient to be able to continue manage teams without having to leave Jira.

Best Regards,
Cornelia

Ashwini Rattihalli

@Cor you can now use the global preview panels to get Team info right in context within Jira or Confluence https://support.atlassian.com/confluence-cloud/docs/view-content-in-a-side-panel/

Cornelia Jeppsson

@Ashwini Rattihalli thanks, but when I navigate to Teams in the left sidebar it takes me to a new tab every time and never in a side-panel... Is there some setting that I can change so that it opens in Jira instead you mean?

Ashwini Rattihalli

@Cor, the behaviour I mentioned is about opening a team linked to a Jira work item. Because Teams App has shared people & teams directory across Atlassian apps, we open the Teams app when you click on the left sidebar, rather than keeping the experience embedded inside Jira. This centralisation keeps the experience consistent across the apps.

Welcome!

It looks like you're new here. Sign in or register to get started.